Local crash via overflowing password length allocation
Published May 20, 2025 · Updated May 21, 2025
Integer overflow in GNU Project PSPP 82fb509fb2fedd33e7ac0c46ca99e108bb3bdffb allows local users to crash pspp-convert via a crafted -l value. In pspp-convert.c, the password-search path passes a size derived from the attacker-controlled maximum length to calloc without rejecting overflow. The path requires local invocation against encrypted input, and exploitation terminates the conversion process.
Summary
What happened
Integer overflow in GNU Project PSPP 82fb509fb2fedd33e7ac0c46ca99e108bb3bdffb allows local users to crash pspp-convert via a crafted -l value. In pspp-convert.c, the password-search path passes a size derived from the attacker-controlled maximum length to calloc without rejecting overflow. The path requires local invocation against encrypted input, and exploitation terminates the conversion process.
The record
- CVE
- CVE-2025-5001
- Published
- May 20, 2025
- Updated
- May 21, 2025
- Vendor
- The GnuPG Project
- Product
- PSPP
- Classifications
- CWE-190, CWE-189
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2025CVE publishedPublication date reported by the CVE source.
- May 21, 2025Record 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=82fb509fb2fedd33e7ac0c46ca99e108bb3bdffb
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- GNU PSPP pspp-convert integer-overflow proof of conceptproof of concept · demonstrated
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