CVE-2025-46399
📋 TL;DR
A NULL pointer dereference vulnerability exists in fig2dev's genge_itp_spline function, allowing local attackers to cause denial of service through input manipulation. This affects systems running vulnerable versions of fig2dev, particularly those processing untrusted local input files. The impact is limited to availability disruption rather than code execution.
💻 Affected Systems
- fig2dev
- transfig
📦 What is this software?
Fig2dev by Fig2dev Project
⚠️ Risk & Real-World Impact
Worst Case
Complete application crash leading to denial of service for fig2dev processes, potentially disrupting workflows that rely on this tool for figure conversion.
Likely Case
Local user can crash fig2dev when processing maliciously crafted input files, causing temporary unavailability of the tool.
If Mitigated
With proper input validation and sandboxing, impact is limited to isolated process crashes without system-wide effects.
🎯 Exploit Status
Exploitation requires local access and ability to run fig2dev with crafted input. No remote exploitation vectors identified.
🛠️ Fix & Mitigation
✅ Official Fix
Patch Version: Distribution-specific (check vendor advisories)
Vendor Advisory: https://access.redhat.com/security/cve/CVE-2025-46399
Restart Required: No
Instructions:
1. Check your distribution's security advisories. 2. Update fig2dev/transfig package using your package manager. 3. For Red Hat-based systems: 'yum update fig2dev'. 4. For Debian/Ubuntu: 'apt update && apt upgrade fig2dev'.
🔧 Temporary Workarounds
Restrict fig2dev execution
linuxLimit fig2dev execution to trusted users only
chmod 750 /usr/bin/fig2dev
setfacl -m u:trusteduser:rx /usr/bin/fig2dev
Input validation wrapper
linuxCreate wrapper script to validate input files before passing to fig2dev
#!/bin/bash
# Validate input file exists and is non-empty
if [ ! -s "$1" ]; then
echo "Invalid input file"
exit 1
fi
/usr/bin/fig2dev "$@"
🧯 If You Can't Patch
- Restrict fig2dev binary permissions to trusted users only
- Implement monitoring for fig2dev process crashes and investigate abnormal patterns
🔍 How to Verify
Check if Vulnerable:
Check fig2dev version: 'fig2dev -v' or 'rpm -q fig2dev' or 'dpkg -l fig2dev'. Compare against patched versions in vendor advisories.Check Version:
fig2dev -v 2>&1 | head -1Verify Fix Applied:
After update, verify version is newer than vulnerable range. Test with known safe input files to ensure functionality.📡 Detection & Monitoring
Log Indicators:
- Segmentation fault errors in system logs involving fig2dev
- Abnormal process termination of fig2dev
Network Indicators:
- None - local vulnerability only
SIEM Query:
process.name:"fig2dev" AND event.action:"process_end" AND exit_code:"139"