How severe is GHSA-4xgv-j62q-h3rj?

GHSA-4xgv-j62q-h3rj has a CVSS score of 5.9/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-4xgv-j62q-h3rj?

GHSA-4xgv-j62q-h3rj affects the following packages: github.com/pion/dtls (Go), github.com/pion/dtls/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-4xgv-j62q-h3rj?

No patched version of github.com/pion/dtls has shipped for GHSA-4xgv-j62q-h3rj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-4xgv-j62q-h3rj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/dtls. 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-4xgv-j62q-h3rj 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-4xgv-j62q-h3rj?

O3 pinpoints whether GHSA-4xgv-j62q-h3rj 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-4xgv-j62q-h3rj actively exploited in the wild?

No public exploit code has been indexed for GHSA-4xgv-j62q-h3rj 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-4xgv-j62q-h3rj published, and has it been updated?

GHSA-4xgv-j62q-h3rj was published on February 7, 2023 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.

🐹 Go

GHSA-4xgv-j62q-h3rj

MEDIUM

Panic during unmarshal of Hello Verify Request in github.com/pion/dtls/v2

Also known asGO-2023-1534

Published

Feb 7, 2023

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

1 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐹github.com/pion/dtls🐹github.com/pion/dtls/v2

Real-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

During the unmarshalling of a hello verify request we could try to unmarshal into too small a buffer. is could result in a panic leading the program to crash.

This issue could be abused to cause a denial of service.

Workaround

None, upgrade to 2.2.4

Affected Packages

2 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/pion/dtls`	all versions	No fix
🐹Go	`github.com/pion/dtls/v2`	all versions	2.2.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/dtls. 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
No patched version of github.com/pion/dtls has shipped for GHSA-4xgv-j62q-h3rj yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-4xgv-j62q-h3rj 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-4xgv-j62q-h3rj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact During the unmarshalling of a hello verify request we could try to unmarshal into too small a buffer. is could result in a panic leading the program to crash. This issue could be abused to cause a denial of service. ### Workaround None, upgrade to 2.2.4

O3 Security · Impact-Aware SCA

Is GHSA-4xgv-j62q-h3rj in your dependencies?

O3 detects GHSA-4xgv-j62q-h3rj across Go 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