Process crash via unbounded filename concatenation
Published Dec 23, 2025 · Updated Dec 23, 2025
Stack-based buffer overflow in GNU Unrtf 0.21.10 allows local users to crash the process via an overlong input filename. The main function copies the filename into a 200-byte stack buffer with strcpy and then appends .rtf with strcat without checking the resulting length. The flaw is reached when Unrtf processes the overlong filename; stack-protected builds abort the converter and interrupt that process.
Summary
What happened
Stack-based buffer overflow in GNU Unrtf 0.21.10 allows local users to crash the process via an overlong input filename. The main function copies the filename into a 200-byte stack buffer with strcpy and then appends .rtf with strcat without checking the resulting length. The flaw is reached when Unrtf processes the overlong filename; stack-protected builds abort the converter and interrupt that process.
The record
- CVE
- CVE-2025-65410
- Published
- Dec 23, 2025
- Updated
- Dec 23, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2025CVE publishedPublication date reported by the CVE source.
- Dec 23, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Overlong filename process-crash 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