GHSA-6qhv-4h7r-2g9m
Fix: trailofbits/rfc3161-client@724a184GHSA-6qhv-4h7r-2g9m is a CWE-347 vulnerability in rfc3161-client. O3 Security confirms whether GHSA-6qhv-4h7r-2g9m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
rfc3161-client has insufficient verification for timestamp response signatures
Real-World Exposure
rfc3161-clientReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
rfc3161-client 1.0.2 and earlier contain a flaw in their timestamp response signature verification logic. In particular, it performs chain verification against the TSR's embedded certificates up to the trusted root(s), but fails to verify the TSR's own signature against the timestamping leaf certificates. Consequently, vulnerable versions perform insufficient signature validation to properly consider a TSR verified, as the attacker can introduce any TSR signature so long as the embedded leaf chains up to some root TSA.
Patches
Users should immediately upgrade to rfc3161-client 1.0.3 or later.
Workarounds
There is no workaround possible. Users should immediately upgrade to a fixed version.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | rfc3161-client | all versions | 1.0.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rfc3161-client. 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 rfc3161-client to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qhv-4h7r-2g9m 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-6qhv-4h7r-2g9m 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-6qhv-4h7r-2g9m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-6qhv-4h7r-2g9m in your dependencies?
O3 detects GHSA-6qhv-4h7r-2g9m across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.