Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-4xgv-j62q-h3rj dtls

MEDIUMFix: pion/dtls@a50d26c

GHSA-4xgv-j62q-h3rj is a medium-severity (CVSS 5.9) vulnerability in github.com/pion/dtls. A fix is available for github.com/pion/dtls — see the affected versions and patch details below.

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
Exploitation data as of Nov 8, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

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
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/pion/dtlsall versionsNo fix
🐹Gogithub.com/pion/dtls/v2all versions2.2.4go get github.com/pion/dtls/v2@v2.2.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/dtls, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4xgv-j62q-h3rj can be triaged on real exposure rather than presence alone.

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 Security finds GHSA-4xgv-j62q-h3rj across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-4xgv-j62q-h3rj: dtls DoS (Medium 5.9) | O3 Security