GHSA-ppjr-267j-5p9x json
NULL pointer derefernce in `stb_image`
published 3y ago modified 3y ago also RUSTSEC-2023-0021
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
A bug in error handling in the `stb_image` C library could cause a NULL pointer dereference when attempting to load an invalid or unsupported image file. This is fixed in version 0.2.5 and later of the `stb_image` Rust crate, by patching the C code to correctly handle NULL pointers.
Patch / fix
Is GHSA-ppjr-267j-5p9x in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | stb_image | <0.2.5 >=0.0.0-0, <0.2.5 |
0.2.5 |
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
-
github.com
/servo/rust-stb-image/pull/102
web
-
github.com
/servo/rust-stb-imag
package
-
rustsec.org
/advisories/RUSTSEC-2023-0021.html
web, advisory
-
crates.io
/crates/stb_image
package
Sources
- GitHub Advisory GHSA-ppjr-267j-5p9x
- OSV RUSTSEC-2023-0021
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.