HighCVE-2017-14099

    Digium Asterisk: security vulnerability (CVE-2017-14099)

    Published Sources: CVE.org

    What is affected, what to do

    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.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Affected
    • Digium Asterisk eq 13.0.0..13.0.0
    • Digium Asterisk eq 13.0.1..13.0.1
    • Digium Asterisk eq 13.0.2..13.0.2
    • Digium Asterisk eq 13.1.0..13.1.0
    • Digium Asterisk eq 13.1.1..13.1.1
    • Digium Asterisk eq 13.2.0..13.2.0
    • Digium Asterisk eq 13.2.1..13.2.1
    • Digium Asterisk eq 13.3.0..13.3.0
    • Digium Asterisk eq 13.3.2..13.3.2
    • Digium Asterisk eq 13.4.0..13.4.0
    • Digium Asterisk eq 13.5.0..13.5.0
    • Digium Asterisk eq 13.6.0..13.6.0
    • Digium Asterisk eq 13.7.0..13.7.0
    • Digium Asterisk eq 13.7.1..13.7.1
    • Digium Asterisk eq 13.7.2..13.7.2
    • Digium Asterisk eq 13.8.0..13.8.0
    • Digium Asterisk eq 13.8.1..13.8.1
    • Digium Asterisk eq 13.8.2..13.8.2
    • Digium Asterisk eq 13.9.0..13.9.0
    • Digium Asterisk eq 13.9.1..13.9.1
    • Digium Asterisk eq 13.10.0..13.10.0
    • Digium Asterisk eq 13.11.0..13.11.0
    • Digium Asterisk eq 13.11.1..13.11.1
    • Digium Asterisk eq 13.11.2..13.11.2
    • Digium Asterisk eq 13.12..13.12
    • Digium Asterisk eq 13.12.0..13.12.0
    • Digium Asterisk eq 13.12.1..13.12.1
    • Digium Asterisk eq 13.12.2..13.12.2
    • Digium Asterisk eq 13.13..13.13
    • Digium Asterisk eq 13.13.0..13.13.0
    • Digium Asterisk eq 13.13.1..13.13.1
    • Digium Asterisk eq 13.14.0..13.14.0
    • Digium Asterisk eq 13.14.1..13.14.1
    • Digium Asterisk eq 13.15.0..13.15.0
    • Digium Asterisk eq 13.15.1..13.15.1
    • Digium Asterisk eq 13.16.0..13.16.0
    • Digium Asterisk eq 13.17.0..13.17.0
    • Digium Asterisk eq 14.0..14.0
    • Digium Asterisk eq 14.0.0..14.0.0
    • Digium Asterisk eq 14.0.1..14.0.1
    • Digium Asterisk eq 14.0.2..14.0.2
    • Digium Asterisk eq 14.1..14.1
    • Digium Asterisk eq 14.01..14.01
    • Digium Asterisk eq 14.1.0..14.1.0
    • Digium Asterisk eq 14.1.1..14.1.1
    • Digium Asterisk eq 14.1.2..14.1.2
    • Digium Asterisk eq 14.02..14.02
    • Digium Asterisk eq 14.2..14.2
    • Digium Asterisk eq 14.2.0..14.2.0
    • Digium Asterisk eq 14.2.1..14.2.1
    • Digium Asterisk eq 14.3.0..14.3.0
    • Digium Asterisk eq 14.3.1..14.3.1
    • Digium Asterisk eq 14.4.0..14.4.0
    • Digium Asterisk eq 14.4.1..14.4.1
    • Digium Asterisk eq 14.5.0..14.5.0
    • Digium Asterisk eq 14.6.0..14.6.0
    • Digium Asterisk eq 11.0.0..11.0.0
    • Digium Asterisk eq 11.0.1..11.0.1
    • Digium Asterisk eq 11.0.2..11.0.2
    • Digium Asterisk eq 11.1.0..11.1.0
    • Digium Asterisk eq 11.1.1..11.1.1
    • Digium Asterisk eq 11.1.2..11.1.2
    • Digium Asterisk eq 11.2.0..11.2.0
    • Digium Asterisk eq 11.2.1..11.2.1
    • Digium Asterisk eq 11.2.2..11.2.2
    • Digium Asterisk eq 11.4.0..11.4.0
    • Digium Asterisk eq 11.6.0..11.6.0
    • Digium Asterisk eq 11.6.1..11.6.1
    • Digium Asterisk eq 11.7.0..11.7.0
    • Digium Asterisk eq 11.8.0..11.8.0
    • Digium Asterisk eq 11.8.1..11.8.1
    • Digium Asterisk eq 11.9.0..11.9.0
    • Digium Asterisk eq 11.10.0..11.10.0
    • Digium Asterisk eq 11.10.1..11.10.1
    • Digium Asterisk eq 11.10.2..11.10.2
    • Digium Asterisk eq 11.11.0..11.11.0
    • Digium Asterisk eq 11.12.0..11.12.0
    • Digium Asterisk eq 11.12.1..11.12.1
    • Digium Asterisk eq 11.13.0..11.13.0
    • Digium Asterisk eq 11.13.1..11.13.1
    • Digium Asterisk eq 11.14.0..11.14.0
    • Digium Asterisk eq 11.14.1..11.14.1
    • Digium Asterisk eq 11.14.2..11.14.2
    • Digium Asterisk eq 11.15.0..11.15.0
    • Digium Asterisk eq 11.15.1..11.15.1
    • Digium Asterisk eq 11.16.0..11.16.0
    • Digium Asterisk eq 11.17.0..11.17.0
    • Digium Asterisk eq 11.17.1..11.17.1
    • Digium Asterisk eq 11.18.0..11.18.0
    • Digium Asterisk eq 11.19.0..11.19.0
    • Digium Asterisk eq 11.20.0..11.20.0
    • Digium Asterisk eq 11.21.0..11.21.0
    • Digium Asterisk eq 11.21.1..11.21.1
    • Digium Asterisk eq 11.21.2..11.21.2
    • Digium Asterisk eq 11.22.0..11.22.0
    • Digium Asterisk eq 11.23.0..11.23.0
    • Digium Asterisk eq 11.23.1..11.23.1
    • Digium Asterisk eq 11.24.0..11.24.0
    • Digium Asterisk eq 11.24.1..11.24.1
    • Digium Asterisk eq 11.25.0..11.25.0
    • Digium Asterisk eq 11.25.1..11.25.1
    • Digium Certified Asterisk eq 11.6..11.6
    • Digium Certified Asterisk eq 13.13..13.13

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.5

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.5

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    4.3 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 91.2

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    104.02 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.5 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.5
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    4.3 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    91.2
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: NVD (NIST), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    digiumasterisk
    • 11.12.1
    • 13.0.0
    • 14.1.1
    • 13.12.1
    • 11.22.0
    • 13.11.2
    • 13.9.1
    • 13.14.0
    • 11.0.0
    • 14.3.0
    • 13.16.0
    • 11.23.1
    • 11.6.0
    • 13.17.0
    • 11.0.1
    • 11.6.1
    • 13.7.2
    • 11.8.0
    • 11.4.0
    • 14.0.0
    • 11.21.2
    • 13.13
    • 13.3.2
    • 11.14.0
    • 13.15.0
    • 13.2.1
    • 11.10.1
    • 14.4.0
    • 11.24.0
    • 11.14.1
    • 13.2.0
    • 13.8.1
    • 14.5.0
    • 14.1
    • 13.8.2
    • 13.7.0
    • 11.7.0
    • 11.12.0
    • 11.9.0
    • 14.0.1
    • 11.16.0
    • 14.1.0
    • 11.1.0
    • 13.1.0
    • 11.10.2
    • 14.3.1
    • 11.25.1
    • 11.21.0
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —

    Vendors and products

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2017-14099
    <a href="https://intel.neosec.eu/en/cve/CVE-2017-14099"><img src="https://intel.neosec.eu/badge/cve/CVE-2017-14099.svg?lang=en" alt="CVE-2017-14099 – NEOSEC Intel" height="20"></a>