CVE-2025-5898

5.3 MEDIUM

📋 TL;DR

A critical out-of-bounds write vulnerability in GNU PSPP's parse_variables_option function allows local attackers to execute arbitrary code or crash the application. This affects users running vulnerable versions of PSPP, particularly those processing untrusted data files. The vulnerability requires local access to exploit.

💻 Affected Systems

Products:
  • GNU PSPP
Versions: Version containing commit 82fb509fb2fedd33e7ac0c46ca99e108bb3bdffb and potentially earlier versions
Operating Systems: Linux, Unix-like systems, Windows
Default Config Vulnerable: ⚠️ Yes
Notes: Vulnerability triggers when processing malicious data files with the pspp-convert utility.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Local privilege escalation leading to full system compromise via arbitrary code execution.

🟠

Likely Case

Application crash (denial of service) or limited code execution in the context of the PSPP process.

🟢

If Mitigated

Minimal impact if proper access controls prevent local users from running malicious PSPP commands.

🌐 Internet-Facing: LOW - Attack requires local access, not remotely exploitable.
🏢 Internal Only: MEDIUM - Local users with access to run PSPP could exploit this vulnerability.

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploit has been publicly disclosed and requires local access to execute malicious PSPP commands.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Check GNU Savannah bug report #67071 for patched version

Vendor Advisory: https://savannah.gnu.org/bugs/index.php?67071

Restart Required: No

Instructions:

1. Check GNU Savannah for patched version. 2. Update PSPP to patched version. 3. Verify fix by testing with proof-of-concept.

🔧 Temporary Workarounds

Restrict PSPP execution

linux

Limit which users can execute PSPP commands to prevent exploitation

chmod 750 /usr/bin/pspp
setfacl -m u:trusteduser:rx /usr/bin/pspp

Avoid processing untrusted files

all

Do not use pspp-convert on untrusted data files from unknown sources

🧯 If You Can't Patch

  • Implement strict access controls to limit which users can run PSPP commands
  • Monitor for suspicious PSPP process execution and file processing activities

🔍 How to Verify

Check if Vulnerable:

Check if PSPP version contains the vulnerable commit 82fb509fb2fedd33e7ac0c46ca99e108bb3bdffb or test with public proof-of-concept

Check Version:

pspp --version

Verify Fix Applied:

Test with the disclosed exploit to confirm it no longer triggers the out-of-bounds write

📡 Detection & Monitoring

Log Indicators:

  • Unusual PSPP process crashes
  • Multiple failed pspp-convert executions
  • Suspicious file processing patterns

Network Indicators:

  • None - local exploitation only

SIEM Query:

Process:pspp OR Process:pspp-convert AND (EventID:1000 OR EventID:1001) OR CommandLine:*malicious*

🔗 References

📤 Share & Export