Memory corruption via unbounded include-path copy
Published Apr 8, 2025 · Updated Apr 8, 2025
Stack-based buffer overflow in stb_include.h at commit f056911 allows remote attackers to corrupt memory via a crafted include path. stb_include_string copies path_to_includes into its fixed 4096-byte temp stack buffer with strcpy, then appends a slash and include filename with strcat without checking the combined length. An embedding application must pass attacker-controlled path data and process an include directive; the overwrite can crash the host process or alter its execution.
Summary
What happened
Stack-based buffer overflow in stb_include.h at commit f056911 allows remote attackers to corrupt memory via a crafted include path. stb_include_string copies path_to_includes into its fixed 4096-byte temp stack buffer with strcpy, then appends a slash and include filename with strcat without checking the combined length. An embedding application must pass attacker-controlled path data and process an include directive; the overwrite can crash the host process or alter its execution.
The record
- CVE
- CVE-2025-3409
- Published
- Apr 8, 2025
- Updated
- Apr 8, 2025
- Vendor
- Sean Barrett
- Product
- stb
- Classifications
- CWE-121, CWE-119, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2025CVE publishedPublication date reported by the CVE source.
- Apr 8, 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=f056911
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
No public exploit references are available in this record.
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