Process-memory corruption via signed class-name length
Published Apr 21, 2026 · Updated Apr 21, 2026
Stack-based buffer overflow in Perl Storable before 3.05 allows attackers to corrupt process memory via a crafted file or buffer. retrieve_hook stores the class-name length in a signed integer but passes it to the read path as unsigned, turning a negative value into an oversized stack-buffer copy. Exploitation requires a Perl process to deserialize attacker-controlled Storable data; the grounded consequence includes process crashes and memory corruption.
Summary
What happened
Stack-based buffer overflow in Perl Storable before 3.05 allows attackers to corrupt process memory via a crafted file or buffer. retrieve_hook stores the class-name length in a signed integer but passes it to the read path as unsigned, turning a negative value into an oversized stack-buffer copy. Exploitation requires a Perl process to deserialize attacker-controlled Storable data; the grounded consequence includes process crashes and memory corruption.
The record
- CVE
- CVE-2017-20230
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- The Perl Foundation
- Product
- Storable
- Classifications
- CWE-121
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.05
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo