# CVE-2022-31031: Potential stack buffer overflow when parsing message as a STUN client

> A stack buffer overflow in PJSIP's STUN client allows attackers to execute arbitrary code or cause denial of service when STUN is enabled.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Jun 2022
- **Updated:** 4 Nov 2025
- **Also known as:** ALPINE-CVE-2022-31031, DEBIAN-CVE-2022-31031, GHSA-26j7-ww69-c4qj, UBUNTU-CVE-2022-31031

## What is CVE-2022-31031?

CVE-2022-31031 is a critical memory corruption vulnerability in Debian Debian Linux, published on 7 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In versions prior to and including 2.12.1 a stack buffer overflow vulnerability affects PJSIP users that use STUN in their applications, either by: setting a STUN server in their account/media config in PJSUA/PJSUA2 level, or directly using `pjlib-util/stun_simple` API. A patch is available in commit 450baca which should be included in the next release. There are no known workarounds for this issue.

Weakness: CWE-787 (Out-of-bounds Write), CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2022-31031?

It affects 2 products.


Products: Debian Debian Linux, Teluu Pjsip.

## How do I fix CVE-2022-31031?

Apply the vendor's patch.

## Is CVE-2022-31031 being exploited?

There is no known exploitation of CVE-2022-31031 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31031 and fix it if it is affected.

What it is: CVE-2022-31031 is a critical memory corruption vulnerability in Debian Debian Linux, published on 7 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31031 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31031/ (Markdown: https://insights.sbomify.com/CVE-2022-31031/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31031
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31031
- OSV: https://osv.dev/vulnerability/CVE-2022-31031

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31031/
Summaries are generated and may contain mistakes; the official description above is the record.