How severe is GHSA-xpp3-xrff-w6rh?

No CVSS score has been assigned to GHSA-xpp3-xrff-w6rh yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xpp3-xrff-w6rh?

GHSA-xpp3-xrff-w6rh affects the following packages: rocksdb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-xpp3-xrff-w6rh?

Update rocksdb to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xpp3-xrff-w6rh is resolved across your whole dependency graph.

How do I detect GHSA-xpp3-xrff-w6rh in my crates.io dependencies?

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

How do I mitigate GHSA-xpp3-xrff-w6rh 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.

Is GHSA-xpp3-xrff-w6rh actively exploited in the wild?

No public exploit code has been indexed for GHSA-xpp3-xrff-w6rh 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-xpp3-xrff-w6rh published, and has it been updated?

GHSA-xpp3-xrff-w6rh was published on August 12, 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

Not in CISA KEV

rocksdb vulnerable to out-of-bounds readGHSA-xpp3-xrff-w6rh

Fix: rust-rocksdb/rust-rocksdb#616

GHSA-xpp3-xrff-w6rh is a security vulnerability in rocksdb. A fix is available for rocksdb — see the affected versions and patch details below.

Also known asRUSTSEC-2022-0046

Published

Aug 12, 2022

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

🦀rocksdb

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

Affected versions of this crate called the RocksDB C API rocksdb_open_column_families_with_ttl() with a pointer to a single integer TTL value, but one TTL value for each column family is expected.

This is only relevant when using rocksdb::DBWithThreadMode::open_cf_descriptors_with_ttl() with multiple column families.

This bug has been fixed in v0.19.0.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rocksdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update rocksdb to 0.19.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xpp3-xrff-w6rh 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.

Frequently Asked Questions

Affected versions of this crate called the RocksDB C API `rocksdb_open_column_families_with_ttl()` with a pointer to a single integer TTL value, but one TTL value for each column family is expected. This is only relevant when using `rocksdb::DBWithThreadMode::open_cf_descriptors_with_ttl()` with multiple column families. This bug has been fixed in v0.19.0.

O3 Security · Impact-Aware SCA

Is GHSA-xpp3-xrff-w6rh in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works