# CVE-2017-14099: Information disclosure in n/a

> Attackers can hijack RTP media streams in Asterisk by exploiting a flaw in strict RTP and symmetric RTP interaction, leading to unauthorized data disclosure.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 2 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-14099, GHSA-4q58-999f-6rpw, UBUNTU-CVE-2017-14099

## What is CVE-2017-14099?

CVE-2017-14099 is a high-severity vulnerability in Digium Asterisk, published on 2 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In res/res_rtp_asterisk.c in Asterisk 11.x before 11.25.2, 13.x before 13.17.1, and 14.x before 14.6.1 and Certified Asterisk 11.x before 11.6-cert17 and 13.x before 13.13-cert5, unauthorized data disclosure (media takeover in the RTP stack) is possible with careful timing by an attacker. The "strictrtp" option in rtp.conf enables a feature of the RTP stack that learns the source address of media for a session and drops any packets that do not originate from the expected address. This option is enabled by default in Asterisk 11 and above. The "nat" and "rtp_symmetric" options (for chan_sip and chan_pjsip, respectively) enable symmetric RTP support in the RTP stack. This uses the source address of incoming media as the target address of any sent media. This option is not enabled by default, but is commonly enabled to handle devices behind NAT. A change was made to the strict RTP support in the RTP stack to better tolerate late media when a reinvite occurs. When combined with the symmetric RTP support, this introduced an avenue where media could be hijacked. Instead of only learning a new address when expected, the new code allowed a new source address to be learned at all times. If a flood of RTP traffic was received, the strict RTP support would allow the new address to provide media, and (with symmetric RTP enabled) outgoing traffic would be sent to this new address, allowing the media to be hijacked. Provided the attacker continued to send traffic, they would continue to receive traffic as well.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2017-14099?

It affects 2 products.


Products: Digium Asterisk, Digium Certified Asterisk.

## How do I fix CVE-2017-14099?

Upgrade to a fixed version.

## Is CVE-2017-14099 being exploited?

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

## Other vulnerabilities in Digium Asterisk

- [CVE-2017-14100](https://insights.sbomify.com/CVE-2017-14100/): Command injection in n/a (critical 9.8)
- [CVE-2014-8418](https://insights.sbomify.com/CVE-2014-8418/): Privilege escalation in n/a (critical 9.0)
- [CVE-2011-1599](https://insights.sbomify.com/CVE-2011-1599/): Missing authorization in n/a (critical 9.0)
- [CVE-2017-16671](https://insights.sbomify.com/CVE-2017-16671/): Memory corruption in n/a (high 8.8)
- [CVE-2017-7617](https://insights.sbomify.com/CVE-2017-7617/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14099 and fix it if it is affected.

What it is: CVE-2017-14099 is a high-severity vulnerability in Digium Asterisk, published on 2 Sep 2017. 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-2017-14099 in the wild and no public exploit code.

Affected product: Digium Asterisk. 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-2017-14099/ (Markdown: https://insights.sbomify.com/CVE-2017-14099/index.md)
```

## Sources

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

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