How severe is GHSA-pfr9-2p92-qrhq?

GHSA-pfr9-2p92-qrhq has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-pfr9-2p92-qrhq?

GHSA-pfr9-2p92-qrhq affects the following packages: dbn (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-pfr9-2p92-qrhq?

Update dbn to 0.22.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfr9-2p92-qrhq is resolved across your whole dependency graph.

How do I detect GHSA-pfr9-2p92-qrhq in my crates.io dependencies?

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

How do I mitigate GHSA-pfr9-2p92-qrhq 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-pfr9-2p92-qrhq?

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

Is GHSA-pfr9-2p92-qrhq actively exploited in the wild?

No public exploit code has been indexed for GHSA-pfr9-2p92-qrhq 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-pfr9-2p92-qrhq published, and has it been updated?

GHSA-pfr9-2p92-qrhq was published on October 9, 2024 and was last updated on May 20, 2026. 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-pfr9-2p92-qrhq — dbn

MEDIUMFix: databento/dbn@339efb9

GHSA-pfr9-2p92-qrhq is a medium-severity (CVSS 5.5) remote code execution vulnerability in dbn. A fix is available for dbn — see the affected versions and patch details below.

Databento Binary Encoding (DBN) has a heap buffer overflow using c_chars_to_str function

Also known asRUSTSEC-2024-0377

Published

Oct 9, 2024

Updated

May 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 20, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀dbn

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

The heap-buffer-overflow is triggered in the strlen() function when handling the c_chars_to_str function in the dbn crate. This vulnerability occurs because the CStr::from_ptr() function in Rust assumes that the provided C string is null-terminated. However, there is no guarantee that the input chars array passed to the c_chars_to_str function is properly null-terminated.

If the chars array does not contain a null byte (\0), strlen() will continue to read beyond the bounds of the buffer in search of a null terminator. This results in an out-of-bounds memory read and can lead to a heap-buffer-overflow, potentially causing memory corruption or exposing sensitive information.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

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

Tailored to GHSA-pfr9-2p92-qrhq. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The `heap-buffer-overflow` is triggered in the `strlen()` function when handling the `c_chars_to_str` function in the dbn crate. This vulnerability occurs because the `CStr::from_ptr()` function in Rust assumes that the provided C string is null-terminated. However, there is no guarantee that the input chars array passed to the c_chars_to_str function is properly null-terminated. If the chars array does not contain a null byte (\0), strlen() will continue to read beyond the bounds of the buffer in search of a null terminator. This results in an out-of-bounds memory read and can lead to a heap

O3 Security · Impact-Aware SCA

Is GHSA-pfr9-2p92-qrhq in your dependencies?

O3 Security finds GHSA-pfr9-2p92-qrhq 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