Bug 2358138 (CVE-2025-3409)

Summary: CVE-2025-3409 stb: Nothings stb stack-based overflow
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: code
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in stb. This vulnerability allows remote attackers to cause a stack-based buffer overflow via manipulation of the path_to_includes argument.
 Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2358165, 2358166, 2358167, 2358168, 2358169, 2358170    
Bug Blocks:    

Description OSIDB Bzimport 2025-04-08 05:01:47 UTC 
A vulnerability classified as critical has been found in Nothings stb up to f056911. This affects the function stb_include_string. The manipulation of the argument path_to_includes leads to stack-based buffer overflow. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The vendor was contacted early about this disclosure but did not respond in any way.
Comment 2 Ben Beasley 2025-04-08 11:00:36 UTC 
The vulnerability report contains little detail. However, the function stb_include_string appears in the stb_include.h library. Significant concerns were noted with the design of this library during package review, so we have never shipped a copy of it:

- It uses strcat/strcpy into a fixed-length buffer that is assumed (but not proven) to be large enough for all possible uses
- It ignores I/O errors (possibly leading to undefined behavior from reading uninitialized memory), and so on.

Since we don’t ship stb_include, we can’t be affected.