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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.8 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N · score source

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

The heap-buffer-overflow is triggered in the strlen() function when handling the ccharstostr function in the dbn crate. This vulnerability occurs because the CStr::fromptr() 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 ccharstostr 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.

Published by the source

9 Oct 2024, 14:34 UTC

Last modified by the source

20 May 2026, 00:56 UTC

Source last checked

26 Oct 2026, 15:42 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-pfr9-2p92-qrhq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-pfr9-2p92-qrhq

Advisory: Databento Binary Encoding (DBN) has a heap buffer overflow using c_chars_to_str function
IDs: GHSA-pfr9-2p92-qrhq
Record: https://patchnext.com/advisories/ghsa-pfr9-2p92-qrhq (revision 1, source checked 26 Oct 2026, 15:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dbn 0.22.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io dbn: affected <= 0.22.0; fixed in 0.22.1

## Suggested inspection (read-only)
- crates.io dbn: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dbn.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-pfr9-2p92-qrhq (GitHub-reviewed advisory GHSA-pfr9-2p92-qrhq lists affected ranges: crates.io dbn >=0 <=0.22.0)

Commands are suggestions: review each one before running it.