Pion/DTLS contains buffer for inbound DTLS fragments with no limit

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2022-29189: 2.15% estimated exploitation activity in the next 30 days; percentile 82.14 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact A buffer that was used for inbound network traffic had no upper limit. Pion DTLS would buffer all network traffic from the remote user until the handshake completes or times out. An attacker could exploit this to cause excessive memory usage. Patches Upgrade to Pion DTLS v2.1.4 Workarounds No workarounds available, upgrade to Pion DTLS v2.1.4 References Thank you to Juho Nurminen and the Mattermost team for discovering and reporting this. For more information If you have any questions or comments about this advisory: Open an issue in Pion DTLS Email us at team@pion.ly

Published by the source

24 May 2022, 22:04 UTC

Last modified by the source

29 Aug 2023, 23:31 UTC

Source last checked

26 Oct 2026, 14:58 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cx94-mrg9-rq4j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-29189

Advisory: Pion/DTLS contains buffer for inbound DTLS fragments with no limit
IDs: CVE-2022-29189, GHSA-cx94-mrg9-rq4j
Record: https://patchnext.com/advisories/cve-2022-29189 (revision 1, source checked 26 Oct 2026, 14:58 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pion/dtls/v2 2.1.4; github.com/pion/dtls 2.1.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pion/dtls/v2: affected < 2.1.4; fixed in 2.1.4
- Go github.com/pion/dtls: affected < 2.1.4; fixed in 2.1.4

## Suggested inspection (read-only)
- Go github.com/pion/dtls/v2: check the installed version with your package manager.
- Go github.com/pion/dtls: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pion/dtls/v2, github.com/pion/dtls.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cx94-mrg9-rq4j (GitHub-reviewed advisory GHSA-cx94-mrg9-rq4j lists affected ranges: Go github.com/pion/dtls >=0 =0 <2.1.4)

Commands are suggestions: review each one before running it.