GHSA-9f3f-wv7r-qc8r
MEDIUMPion DTLS's usage of random nonce generation with AES GCM ciphers risks leaking the authentication key
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
github.com/pion/dtls/v3🐹github.com/pion/dtls/v2🐹github.com/pion/dtls🐹github.com/pion/dtls/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Pion DTLS versions v1.0.0 through v3.0.10 use random nonce generation with AES GCM ciphers, which makes it easier for remote attackers to obtain the authentication key and spoof data by leveraging the reuse of a nonce in a session and a "forbidden attack".
Patches
Upgrade to v3.1.1 or later. This version includes PR #796, which uses the 64-bit sequence number to populate the nonce_explicit part of the GCM nonce. This is according to best practice outlined in RFC 9325 section 7.2.1.
v3.0.11 is a backport patch supporting Go v1.21
Workarounds
There are no workarounds without upgrading to version v3.0.11, v3.1.1 or later.
References
Commit fixing the bug: https://github.com/pion/dtls/commit/61762dee8217991882c5eb79856b9e7a73ee349f Commit fixing the bug (backport): 90e241c Pull request: #796
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/pion/dtls/v3 | ≥ 3.1.0&&< 3.1.1 | 3.1.1 |
| 🐹Go | github.com/pion/dtls/v2 | all versions | No fix |
| 🐹Go | github.com/pion/dtls | all versions | No fix |
| 🐹Go | github.com/pion/dtls/v3 | all versions | 3.0.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/dtls/v3. 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 github.com/pion/dtls/v3 to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9f3f-wv7r-qc8r 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-9f3f-wv7r-qc8r 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-9f3f-wv7r-qc8r. 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-9f3f-wv7r-qc8r in your dependencies?
O3 detects GHSA-9f3f-wv7r-qc8r across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.