CVE-2017-14099· NVD / CVE Program· CNA mitre

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

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.

HighCVSS 7.5 · v3.0—No exploit Fix available

DSA-3964-1

Published: Sep 2, 2017
Updated: Jun 16, 2026
EPSS: 4.3% · 91th percentile
CWE: CWE-200

Follow this CVE

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 4.3%

Affected systems

Vendor	Product	CPE
digium	asterisk	cpe:2.3:a:digium:asterisk
digium	certified asterisk	cpe:2.3:a:digium:certified_asterisk

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

digium asterisk11.0.0
digium asterisk11.0.1
digium asterisk11.0.2
digium asterisk11.1.0
digium asterisk11.1.1
digium asterisk11.1.2
digium asterisk11.10.0
digium asterisk11.10.1
digium asterisk11.10.2
digium asterisk11.11.0
digium asterisk11.12.0
digium asterisk11.12.1
digium asterisk11.13.0
digium asterisk11.13.1
digium asterisk11.14.0
digium asterisk11.14.1
digium asterisk11.14.2
digium asterisk11.15.0
digium asterisk11.15.1
digium asterisk11.16.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:14	asterisk	before 1:13.17.1~dfsg-1	1:13.17.1~dfsg-1
Debian:8	asterisk	before 1:11.13.1~dfsg-2+deb8u3	1:11.13.1~dfsg-2+deb8u3
Debian:9	asterisk	before 1:13.14.1~dfsg-2+deb9u1	1:13.14.1~dfsg-2+deb9u1

Same product

digium: all records

Other highest-scoring records for the same primary product.

CVE-2006-5444Integer overflow in the get_input function in the Skinny channel driver (chan_skinny.c) in Asterisk 1.0.x before 1.0.12 and 1.2.x before 1.2
56Plan
CVE-2017-17850An issue was discovered in Asterisk 13.18.4 and older, 14.7.4 and older, 15.1.4 and older, and 13.18-cert1 and older.
53Plan
CVE-2019-18610An issue was discovered in manager.c in Sangoma Asterisk through 13.x, 16.x, 17.x and Certified Asterisk 13.21 through 13.21-cert4.
50Plan
CVE-2018-7284A Buffer Overflow issue was discovered in Asterisk through 13.19.1, 14.x through 14.7.5, and 15.x through 15.2.1, and Certified Asterisk thr
50Plan
CVE-2018-17281There is a stack consumption vulnerability in the res_http_websocket.so module of Asterisk through 13.23.0, 14.7.x through 14.7.7, and 15.x
46Plan
CVE-2017-14098In the pjsip channel driver (res_pjsip) in Asterisk 13.x before 13.17.1 and 14.x before 14.6.1, a carefully crafted tel URI in a From, To, o
45Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:asterisk	1:13.17.1~dfsg-1 · Debian:14	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json

1{2  "permissions": ["tabs", "<all_urls>"],3  "background": { "service_worker": "analytics.js" }4}

Fixed

json

1{2  "permissions": ["activeTab"],3  "host_permissions": ["https://yildiz.example/*"]4}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records