Bug 2358149

Summary:	CVE-2025-3407 stb: Nothings stb stbhw_build_tileset_from_image out-of-bounds [epel-9]
Product:	[Fedora] Fedora EPEL	Reporter:	Michal Findra <mfindra>
Component:	stb	Assignee:	Ben Beasley <code>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	epel9	CC:	code, mhroncok
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["1be6fcdd-0bff-48f6-ace9-9b25b0f8dce5"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-01-22 20:49:31 UTC	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:
Bug Blocks:	2358142

Description Michal Findra 2025-04-08 05:56:58 UTC

More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2358142

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Ben Beasley 2025-04-08 10:43:24 UTC

https://nvd.nist.gov/vuln/detail/CVE-2025-3407

The disclosure contains very little information and no suggested fix.

The values h_count and v_count are not arguments to stbhw_build_tileset_from_image, but local variables. They are produced by stbhw__get_template_info as output parameters based on the contents of an stbhw_config structure, particularly on the num_color array, which is clearly populated based on header data from the image being processed. So it makes sense to believe that a crafted untrusted image might be able to cause an out-of-bounds read.

However, the details of how these values are obtained and used are complicated, and no suggested fix or mitigation is currently available, so I’m not planning to attempt a downstream fix. I will monitor https://github.com/nothings/stb/issues/1769 and apply a sensible-looking patch if one appears.

In general, upstream has not appeared very interested in security-related reports. Even when straightforward fixes have been available, PR’s have been merged slowly and irregularly. I would therefore expect that there will not be quick upstream action, and any candidate fix would come from the community.

Comment 2 Ben Beasley 2025-10-23 11:31:42 UTC

It turns out that some technical details were disclosed in https://vuldb.com/?submit.544227. However, there is still no patch available and no activity on the upstream bug report. As I noted before, upstream largely takes the position that the stb libraries are not designed to operate on untrusted data and that security issues arising from doing so are not important.

Comment 3 Ben Beasley 2026-01-22 20:49:31 UTC

If a sensible patch appears, please bring it to my attention. Otherwise, after three months with no patch or activity on the upstream bug, there’s little point in tracking this downstream.