Application crash via reachable variable assertion
Published May 3, 2025 · Updated May 5, 2025
Reachable assertion in GNU PSPP 2.0.1 and earlier allows local users to crash the application by processing crafted input data. Dictionary handling passes the crafted data into variable.c, where var_set_leave_quiet reaches an assertion and forces application exit. Local access and the ability to make PSPP process the data are required; the reported consequence is termination of that PSPP process.
Summary
What happened
Reachable assertion in GNU PSPP 2.0.1 and earlier allows local users to crash the application by processing crafted input data. Dictionary handling passes the crafted data into variable.c, where var_set_leave_quiet reaches an assertion and forces application exit. Local access and the ability to make PSPP process the data are required; the reported consequence is termination of that PSPP process.
The record
- CVE
- CVE-2025-47229
- Published
- May 3, 2025
- Updated
- May 5, 2025
- Vendor
- The GnuPG Project
- Product
- PSPP
- Classifications
- CWE-617, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 3, 2025CVE publishedPublication date reported by the CVE source.
- May 5, 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=0 <=2.0.1
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 Savannah bug 67049 proof of conceptproof of concept · unverified
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