How severe is GHSA-ppjr-267j-5p9x?

No CVSS score has been assigned to GHSA-ppjr-267j-5p9x yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-ppjr-267j-5p9x?

GHSA-ppjr-267j-5p9x affects the following packages: stb_image (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-ppjr-267j-5p9x?

Update stb_image to 0.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ppjr-267j-5p9x is resolved across your whole dependency graph.

How do I detect GHSA-ppjr-267j-5p9x in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for stb_image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-ppjr-267j-5p9x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-ppjr-267j-5p9x?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ppjr-267j-5p9x can be triaged on real exposure rather than presence alone.

Is GHSA-ppjr-267j-5p9x actively exploited in the wild?

No public exploit code has been indexed for GHSA-ppjr-267j-5p9x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-ppjr-267j-5p9x published, and has it been updated?

GHSA-ppjr-267j-5p9x was published on March 20, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-ppjr-267j-5p9x — stb_image

Fix: servo/rust-stb-image#102

GHSA-ppjr-267j-5p9x is a security vulnerability in stb_image. A fix is available for stb_image — see the affected versions and patch details below.

NULL pointer derefernce in `stb_image`

Also known asRUSTSEC-2023-0021

Published

Mar 20, 2023

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀stb_image

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`stb_image`	all versions	0.2.5`cargo update -p stb_image --precise 0.2.5`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for stb_image, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update stb_image to 0.2.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ppjr-267j-5p9x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-ppjr-267j-5p9x can be triaged on real exposure rather than presence alone.

Tailored to GHSA-ppjr-267j-5p9x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-ppjr-267j-5p9x in your dependencies?

O3 Security finds GHSA-ppjr-267j-5p9x across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works