How severe is GHSA-48vq-8jqv-gm6f?

No CVSS score has been assigned to GHSA-48vq-8jqv-gm6f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-48vq-8jqv-gm6f?

GHSA-48vq-8jqv-gm6f affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-48vq-8jqv-gm6f?

Update ckb to 0.40.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-48vq-8jqv-gm6f is resolved across your whole dependency graph.

How do I detect GHSA-48vq-8jqv-gm6f in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckb. 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-48vq-8jqv-gm6f 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-48vq-8jqv-gm6f?

O3 pinpoints whether GHSA-48vq-8jqv-gm6f 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-48vq-8jqv-gm6f actively exploited in the wild?

No public exploit code has been indexed for GHSA-48vq-8jqv-gm6f 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.

What type of vulnerability is GHSA-48vq-8jqv-gm6f?

GHSA-48vq-8jqv-gm6f is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-48vq-8jqv-gm6f published, and has it been updated?

GHSA-48vq-8jqv-gm6f was published on August 25, 2021 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

GHSA-48vq-8jqv-gm6f

GHSA-48vq-8jqv-gm6f is a CWE-770 vulnerability in ckb. O3 Security confirms whether GHSA-48vq-8jqv-gm6f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Remote memory exhaustion in ckb

Also known asCVE-2021-45699 GHSA-2969-8hh9-57jcRUSTSEC-2021-0108

Published

Aug 25, 2021

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀ckb

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

A remote attacker can manipulate this HashMap to grow forever, resulting in degraded performance and ultimately a panic on allocation failure or being killed by the OS, depending on the platform.

This is a critical severity security bug. It could be exploited to create a targeted or network-wide denial of service, to reduce the hash power of the network as part of a 51% attack, and perhaps in other creative ways.

An attack is trivial:

connect to another node
send an invalid sync protocol request, such as SendHeaders for non-consecutive blocks
disconnect
repeat

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	all versions	0.40.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ckb. 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 ckb to 0.40.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-48vq-8jqv-gm6f 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-48vq-8jqv-gm6f 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-48vq-8jqv-gm6f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In the ckb sync protocol, SyncState maintains a HashMap called 'misbehavior' that keeps a score of a peer's violations of the protocol. This HashMap is keyed to PeerIndex (an alias for SessionId), and entries are never removed from it. SessionId is an integer that increases monotonically with every new connection. A remote attacker can manipulate this HashMap to grow forever, resulting in degraded performance and ultimately a panic on allocation failure or being killed by the OS, depending on the platform. This is a critical severity security bug. It could be exploited to create a targeted o

O3 Security · Impact-Aware SCA

Is GHSA-48vq-8jqv-gm6f in your dependencies?

O3 detects GHSA-48vq-8jqv-gm6f 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