Summary
Workaround
None
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.
A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.
GHSA-HXP2-XQF3-V83H has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2.4); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-HXP2-XQF3-V83H? GHSA-HXP2-XQF3-V83H is a medium-severity out-of-bounds read vulnerability in github.com/pion/dtls/v2 (go), affecting versions < 2.2.4. It is fixed in 2.2.4. A read operation accesses a memory location beyond the intended buffer boundary.
- How severe is GHSA-HXP2-XQF3-V83H? GHSA-HXP2-XQF3-V83H has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by GHSA-HXP2-XQF3-V83H?
github.com/pion/dtls/v2(go) (versions < 2.2.4)github.com/pion/dtls(go) (versions <= 1.5.4)
- Is there a fix for GHSA-HXP2-XQF3-V83H? Yes. GHSA-HXP2-XQF3-V83H is fixed in 2.2.4. Upgrade to this version or later.
- Is GHSA-HXP2-XQF3-V83H exploitable, and should I be worried? Whether GHSA-HXP2-XQF3-V83H is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-HXP2-XQF3-V83H is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-HXP2-XQF3-V83H? Upgrade
github.com/pion/dtls/v2to 2.2.4 or later.