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

Q: How do I fix CVE-2017-14114?

rtpproxy: upgrade to newer than 2.2. Exact commands for each OS are on this page.

Q: Is CVE-2017-14114 being exploited?

CVE-2017-14114 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-14114 affect?

CVE-2017-14114 affects rtpproxy. Severity is medium (CVSS 6.5). 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

Q: How urgent is CVE-2017-14114?

Priority 46/100. Remotely exploitable, no login, no user action

This month

MEDIUM 6.5REMOTEUPGRADE

CVE-2017-14114 is a medium-severity flaw (CVSS 6.5) affecting rtpproxy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.4% (top 27%)
CISA exploited list	No
Weakness	CWE-200
Published	2017-09-02
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: rtpproxy

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-09-02 16:29 UTCPublished CVE record published
2026-06-17 01:05 UTCUpdated Record last modified

rtpproxy rtpproxy UPGRADE

Affected: <= 2.2

Fixed in: newer than 2.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy rtpproxy || rpm -q rtpproxy || rtpproxy --version

2. UPGRADE to newer than 2.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade rtpproxy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade rtpproxy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-14114?

rtpproxy: upgrade to newer than 2.2. Exact commands for each OS are on this page.

Is CVE-2017-14114 being exploited?

CVE-2017-14114 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-14114 affect?

CVE-2017-14114 affects rtpproxy. Severity is medium (CVSS 6.5). 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

How urgent is CVE-2017-14114?

Priority 46/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs