GHSA-g4h2-4wvh-grc5 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in simple_asn1. A fix is available for simple_asn1 — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
simple_asn1Real-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
An issue was discovered in the simple_asn1 crate 0.6.0 before 0.6.1 for Rust. There is a panic if UTCTime data, supplied by a remote attacker, has a second character greater than 0x7f.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | simple_asn1 | ≥ 0.6.0&&< 0.6.1 | 0.6.1cargo update -p simple_asn1 --precise 0.6.1 |
Affected Products
simple asn1simple_asn1_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for simple_asn1, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update simple_asn1 to 0.6.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g4h2-4wvh-grc5 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
Is GHSA-g4h2-4wvh-grc5 in your dependencies?
Find it across crates.io, including transitive dependencies.