How severe is GHSA-hxp2-xqf3-v83h?

GHSA-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h?

GHSA-hxp2-xqf3-v83h affects the following packages: github.com/pion/dtls (Go), github.com/pion/dtls/v2 (Go). Ecosystems affected: Go.

How do I fix GHSA-hxp2-xqf3-v83h?

No patched version of github.com/pion/dtls has shipped for GHSA-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h?

O3 pinpoints whether GHSA-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h actively exploited in the wild?

No public exploit code has been indexed for GHSA-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h published, and has it been updated?

GHSA-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h

MEDIUM

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

Also known asGO-2023-1535

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

When attempting to unmarshal a Server Hello request we could attempt to unmarshal into a buffer that was too small. This could result in a panic leading the program to crash.

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

Workaround

None

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-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h 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-hxp2-xqf3-v83h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact When attempting to unmarshal a Server Hello request we could attempt to unmarshal into a buffer that was too small. This could result in a panic leading the program to crash. This issue could be abused to cause a denial of service. ### Workaround None

O3 Security · Impact-Aware SCA

Is GHSA-hxp2-xqf3-v83h in your dependencies?

O3 detects GHSA-hxp2-xqf3-v83h 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