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

> Remote attackers can obtain sensitive information or cause denial of service via crafted RTP packets due to improper NAT handling in RTPproxy.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-pxw2-p26j-qh83, UBUNTU-CVE-2017-14114

## What is CVE-2017-14114?

CVE-2017-14114 is a medium-severity vulnerability in n/a, published on 2 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RTPproxy through 2.2.alpha.20160822 has a NAT feature that results in not properly determining the IP address and port number of the legitimate recipient of RTP traffic, which allows remote attackers to obtain sensitive information or cause a denial of service (communication outage) via crafted RTP packets.

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

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

It affects 1 product.


Products: Rtpproxy Rtpproxy.

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

No fix has been published for CVE-2017-14114 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-14114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14114 is a medium-severity vulnerability in n/a, 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-14114 in the wild and no public exploit code.

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

## Sources

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

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