Process crash via malformed SPV trailing content
Published May 10, 2025 · Updated May 12, 2025
Out-of-bounds read in GNU PSPP 2.0.1 and earlier allows local users to crash pspp-output by processing a malformed SPV document. When extra content follows the XML document, spvxml_parse_attributes in spvxml-helpers.c reads through an invalid near-null address. A local user must supply the malformed SPV content to pspp-output; the demonstrated consequence is a single-process abort, with no sourced data disclosure or code execution.
Summary
What happened
Out-of-bounds read in GNU PSPP 2.0.1 and earlier allows local users to crash pspp-output by processing a malformed SPV document. When extra content follows the XML document, spvxml_parse_attributes in spvxml-helpers.c reads through an invalid near-null address. A local user must supply the malformed SPV content to pspp-output; the demonstrated consequence is a single-process abort, with no sourced data disclosure or code execution.
The record
- CVE
- CVE-2025-47816
- Published
- May 10, 2025
- Updated
- May 12, 2025
- Vendor
- The GnuPG Project
- Product
- PSPP
- Classifications
- CWE-125
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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.
Weakness, pattern, technique
Public exploit references
- Malformed SPV document 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