How severe is GHSA-v8gq-5grq-9728?

No CVSS score has been assigned to GHSA-v8gq-5grq-9728 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v8gq-5grq-9728?

GHSA-v8gq-5grq-9728 affects the following packages: mozjpeg (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-v8gq-5grq-9728?

Update mozjpeg to 0.8.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v8gq-5grq-9728 is resolved across your whole dependency graph.

How do I detect GHSA-v8gq-5grq-9728 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mozjpeg. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-v8gq-5grq-9728 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-v8gq-5grq-9728?

O3 pinpoints whether GHSA-v8gq-5grq-9728 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-v8gq-5grq-9728 actively exploited in the wild?

No public exploit code has been indexed for GHSA-v8gq-5grq-9728 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-v8gq-5grq-9728 published, and has it been updated?

GHSA-v8gq-5grq-9728 was published on September 16, 2022 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

GHSA-v8gq-5grq-9728

mozjpeg DecompressScanlines::read_scanlines is Unsound

Also known asRUSTSEC-2020-0165

Published

Sep 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🦀mozjpeg

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

This issue and vector is similar to RUSTSEC-2020-0029 of rgb crate which mozjpeg depends on.

Affected versions of mozjpeg crate allow creating instances of any type T from bytes, and do not correctly constrain T to the types for which it is safe to do so.

Examples of safety violation possible for a type T:

T contains a reference type, and it constructs a pointer to an invalid, arbitrary memory address.
T requires a safety and/or validity invariant for its construction that may be violated.

The issue was fixed in 0.8.19 by using safer types and involving rgb dependency bump.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`mozjpeg`	all versions	0.8.19

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mozjpeg. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mozjpeg to 0.8.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v8gq-5grq-9728 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 pinpoints whether GHSA-v8gq-5grq-9728 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-v8gq-5grq-9728. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

This issue and vector is similar to [RUSTSEC-2020-0029] of `rgb` crate which `mozjpeg` depends on. Affected versions of `mozjpeg` crate allow creating instances of any type `T` from bytes, and do not correctly constrain `T` to the types for which it is safe to do so. Examples of safety violation possible for a type `T`: * `T` contains a reference type, and it constructs a pointer to an invalid, arbitrary memory address. * `T` requires a safety and/or validity invariant for its construction that may be violated. The issue was fixed in 0.8.19 by using safer types and involving `rgb` dependen

O3 Security · Impact-Aware SCA

Is GHSA-v8gq-5grq-9728 in your dependencies?

O3 detects GHSA-v8gq-5grq-9728 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works