How severe is GHSA-mc39-h54g-pvw6?

GHSA-mc39-h54g-pvw6 has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-mc39-h54g-pvw6?

GHSA-mc39-h54g-pvw6 affects the following packages: libdav1d-sys (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-mc39-h54g-pvw6?

Update libdav1d-sys to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mc39-h54g-pvw6 is resolved across your whole dependency graph.

How do I detect GHSA-mc39-h54g-pvw6 in my crates.io dependencies?

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

How do I mitigate GHSA-mc39-h54g-pvw6 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-mc39-h54g-pvw6?

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

Is GHSA-mc39-h54g-pvw6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mc39-h54g-pvw6 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-mc39-h54g-pvw6 published, and has it been updated?

GHSA-mc39-h54g-pvw6 was published on April 5, 2024 and was last updated on April 11, 2024. 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

MEDIUM severity

GHSA-mc39-h54g-pvw6 — libdav1d-sys

MEDIUM

GHSA-mc39-h54g-pvw6 is a medium-severity (CVSS 5.9) remote code execution vulnerability in libdav1d-sys. A fix is available for libdav1d-sys — see the affected versions and patch details below.

libdav1d-sys affected by dav1d AV1 decoder integer overflow

Also known asRUSTSEC-2024-0016

Published

Apr 5, 2024

Updated

Apr 11, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Apr 11, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀libdav1d-sys

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

An integer overflow in dav1d AV1 decoder that can occur when decoding videos with large frame size. This can lead to memory corruption within the AV1 decoder. We recommend upgrading to version 0.7.0 of libdav1d-sys, which includes dav1d 1.4.0.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libdav1d-sys`	all versions	0.7.0`cargo update -p libdav1d-sys --precise 0.7.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libdav1d-sys, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update libdav1d-sys to 0.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mc39-h54g-pvw6 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-mc39-h54g-pvw6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mc39-h54g-pvw6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-mc39-h54g-pvw6 in your dependencies?

O3 Security finds GHSA-mc39-h54g-pvw6 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