HIGH CVSS 7.5
Published: 2017-09-02

CVE-2017-14099

digium asterisk Security Advisory (CVE-2017-14099)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2017-14099?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2017-14099 impacting digium asterisk. Evaluated with CVSS Base Score of 7.5 (HIGH).

Original NVD Description

Source: NIST NVD
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.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
None (I:N)
No system modification impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product digium / asterisk
Affected Versions 13.0.0
Weakness Enumeration CWE-200

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2017-14099 impacting digium asterisk.

⚡ Nuclei Detection Template (YAML) cve-2017-14099.yaml
id: cve-2017-14099

info:
  name: digium asterisk - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2017-14099 affecting digium asterisk.
    Evaluation: 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 ...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2017-14099
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 7.5
    cve-id: CVE-2017-14099
    cwe-id: CWE-200
  tags: cve,cve-2017-14099,digium,asterisk,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "asterisk"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2017-14099.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2017-14099
# Target: digium asterisk | CVSS: 7.5 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2017-14099 (digium asterisk)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against digium asterisk scope (13.0.0).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2017-14099.sh
# Recommended Remediation & Patching Commands for CVE-2017-14099
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install asterisk 2>/dev/null || \
sudo dnf upgrade asterisk 2>/dev/null || \
sudo yum update asterisk

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i asterisk 2>/dev/null || rpm -qa | grep -i asterisk

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2017-14099 in digium asterisk?

Review vendor-specific security notices and update digium asterisk packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2017-14099?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2017-14099?

CVE-2017-14099 is classified with a CVSS 3.1 Base Score of 7.5 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
7.5
HIGH SEVERITY
CVE ID CVE-2017-14099
Weakness CWE-200
Vendor digium
Product asterisk
Published 2017-09-02
Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N