# CVE-2022-39269: Media transport downgrade from the secure version (SRTP) to non-secure (RTP) in pjsip

> Attackers can force PJSIP to downgrade secure SRTP media to insecure RTP, exposing communication content to eavesdropping.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2022
- **Updated:** 23 Apr 2025
- **Also known as:** ALPINE-CVE-2022-39269, DEBIAN-CVE-2022-39269, GHSA-wx5m-cj97-4wwg, UBUNTU-CVE-2022-39269

## What is CVE-2022-39269?

CVE-2022-39269 is a critical vulnerability in pjsip pjproject, published on 6 Oct 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. When processing certain packets, PJSIP may incorrectly switch from using SRTP media transport to using basic RTP upon SRTP restart, causing the media to be sent insecurely. The vulnerability impacts all PJSIP users that use SRTP. The patch is available as commit d2acb9a in the master branch of the project and will be included in version 2.13. Users are advised to manually patch or to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Teluu Pjsip.

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

Upgrade to a fixed version.

## Is CVE-2022-39269 being exploited?

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

## Other vulnerabilities in pjsip pjproject

- [CVE-2023-38703](https://insights.sbomify.com/CVE-2023-38703/): PJSIP has use-after-free vulnerability in SRTP media transport (critical 9.8)
- [CVE-2026-57161](https://insights.sbomify.com/CVE-2026-57161/): PJSIP: Stack overflow handling Service-Route headers in a registration response (high 8.8)
- [CVE-2026-57162](https://insights.sbomify.com/CVE-2026-57162/): PJSIP: Stack overflow parsing SDP a=crypto attributes (high 8.8)
- [CVE-2026-57163](https://insights.sbomify.com/CVE-2026-57163/): PJSIP: Stack overflow parsing a TLS peer certificate's SubjectAltName in GnuTLS backend (high 8.8)
- [CVE-2026-57159](https://insights.sbomify.com/CVE-2026-57159/): PJSIP: SDP parser out-of-bounds write in remote payload-type map maintenance (high 8.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-39269 is a critical vulnerability in pjsip pjproject, published on 6 Oct 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-39269 in the wild and no public exploit code.

Affected product: pjsip pjproject. 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-39269/ (Markdown: https://insights.sbomify.com/CVE-2022-39269/index.md)
```

## Sources

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

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