How severe is GHSA-mcmr-49x3-4jqm?

No CVSS score has been assigned to GHSA-mcmr-49x3-4jqm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mcmr-49x3-4jqm?

GHSA-mcmr-49x3-4jqm affects the following packages: ckb (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-mcmr-49x3-4jqm?

Update ckb to 0.102.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcmr-49x3-4jqm is resolved across your whole dependency graph.

How do I detect GHSA-mcmr-49x3-4jqm in my crates.io dependencies?

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

How do I mitigate GHSA-mcmr-49x3-4jqm 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-mcmr-49x3-4jqm?

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

Is GHSA-mcmr-49x3-4jqm actively exploited in the wild?

No public exploit code has been indexed for GHSA-mcmr-49x3-4jqm 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-mcmr-49x3-4jqm published, and has it been updated?

GHSA-mcmr-49x3-4jqm was published on November 2, 2022. 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-mcmr-49x3-4jqm — ckb

GHSA-mcmr-49x3-4jqm is a security vulnerability in ckb. A fix is available for ckb — see the affected versions and patch details below.

ckb type_id script resume may randomly fail

Published

Nov 2, 2022

Updated

Nov 2, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2022 · OSV.dev, 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

Impact

https://github.com/nervosnetwork/ckb/blob/v0.101.2/script/src/verify.rs#L871-L879 TypeIdSystemScript resume handle is not correct when max_cycles is not enough, ScriptError::ExceededMaximumCycles will be raised directly ranther than suspend as expect, and also because script_group execution order is random, so this will happen randomly.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`ckb`	≥ 0.100.0&&< 0.102.0	0.102.0`cargo update -p ckb --precise 0.102.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ckb to 0.102.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mcmr-49x3-4jqm 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-mcmr-49x3-4jqm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mcmr-49x3-4jqm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact https://github.com/nervosnetwork/ckb/blob/v0.101.2/script/src/verify.rs#L871-L879 TypeIdSystemScript resume handle is not correct when max_cycles is not enough, `ScriptError::ExceededMaximumCycles` will be raised directly ranther than suspend as expect, and also because script_group execution order is random, so this will happen randomly.

O3 Security · Impact-Aware SCA

Is GHSA-mcmr-49x3-4jqm in your dependencies?

O3 Security finds GHSA-mcmr-49x3-4jqm 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