ID CVE-2017-16672
Summary An issue was discovered in Asterisk Open Source 13 before 13.18.1, 14 before 14.7.1, and 15 before 15.1.1 and Certified Asterisk 13.13 before 13.13-cert7. A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. Eventually Asterisk can run out of memory and crash.
References
Vulnerable Configurations
  • Digium Asterisk 13.0.0 LTS
    cpe:2.3:a:digium:asterisk:13.0.0:-:-:-:lts
  • Digium Asterisk 13.0.0 Beta 1
    cpe:2.3:a:digium:asterisk:13.0.0:beta1
  • Digium Asterisk 13.0.0 Beta 2
    cpe:2.3:a:digium:asterisk:13.0.0:beta2
  • Digium Asterisk 13.0.0 Beta 3
    cpe:2.3:a:digium:asterisk:13.0.0:beta3
  • Digium Asterisk 13.0.1
    cpe:2.3:a:digium:asterisk:13.0.1
  • Digium Asterisk 13.0.2
    cpe:2.3:a:digium:asterisk:13.0.2
  • Digium Asterisk 13.1.0
    cpe:2.3:a:digium:asterisk:13.1.0
  • Digium Asterisk 13.1.0 release candidate 1
    cpe:2.3:a:digium:asterisk:13.1.0:rc1
  • Digium Asterisk 13.1.0 release candidate 2
    cpe:2.3:a:digium:asterisk:13.1.0:rc2
  • Digium Asterisk 13.1.1
    cpe:2.3:a:digium:asterisk:13.1.1
  • Digium Asterisk 13.2.0
    cpe:2.3:a:digium:asterisk:13.2.0
  • Digium Asterisk 13.2.0 release candidate 1
    cpe:2.3:a:digium:asterisk:13.2.0:rc1
  • Digium Asterisk 13.2.1
    cpe:2.3:a:digium:asterisk:13.2.1
  • Digium Asterisk 13.3.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.3.0:rc1
  • Digium Asterisk 13.3.2
    cpe:2.3:a:digium:asterisk:13.3.2
  • Digium Asterisk 13.4.0
    cpe:2.3:a:digium:asterisk:13.4.0
  • Digium Asterisk 13.4.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.4.0:rc1
  • Digium Asterisk 13.5.0
    cpe:2.3:a:digium:asterisk:13.5.0
  • Digium Asterisk 13.5.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.5.0:rc1
  • Digium Asterisk 13.6.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.6.0:rc1
  • Digium Asterisk 13.7.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.7.0:rc1
  • Digium Asterisk 13.7.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:13.7.0:rc2
  • Digium Asterisk 13.7.1
    cpe:2.3:a:digium:asterisk:13.7.1
  • Digium Asterisk 13.7.2
    cpe:2.3:a:digium:asterisk:13.7.2
  • Digium Asterisk 13.8.0
    cpe:2.3:a:digium:asterisk:13.8.0
  • Digium Asterisk 13.8.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.8.0:rc1
  • Digium Asterisk 13.8.1
    cpe:2.3:a:digium:asterisk:13.8.1
  • Digium Asterisk 13.8.2
    cpe:2.3:a:digium:asterisk:13.8.2
  • Digium Asterisk 13.9.0
    cpe:2.3:a:digium:asterisk:13.9.0
  • Digium Asterisk 13.9.1
    cpe:2.3:a:digium:asterisk:13.9.1
  • Digium Asterisk 13.10.0
    cpe:2.3:a:digium:asterisk:13.10.0
  • Digium Asterisk 13.10.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.10.0:rc1
  • Digium Asterisk 13.11.0
    cpe:2.3:a:digium:asterisk:13.11.0
  • Digium Asterisk 13.11.1
    cpe:2.3:a:digium:asterisk:13.11.1
  • Digium Asterisk 13.11.2
    cpe:2.3:a:digium:asterisk:13.11.2
  • Digium Asterisk 13.12
    cpe:2.3:a:digium:asterisk:13.12
  • Digium Asterisk 13.12.0
    cpe:2.3:a:digium:asterisk:13.12.0
  • Digium Asterisk 13.12.1
    cpe:2.3:a:digium:asterisk:13.12.1
  • Digium Asterisk 13.12.2
    cpe:2.3:a:digium:asterisk:13.12.2
  • Digium Asterisk 13.13
    cpe:2.3:a:digium:asterisk:13.13
  • Digium Asterisk 13.13.0
    cpe:2.3:a:digium:asterisk:13.13.0
  • Digium Asterisk 13.13.1
    cpe:2.3:a:digium:asterisk:13.13.1
  • Digium Asterisk 13.14.0
    cpe:2.3:a:digium:asterisk:13.14.0
  • Digium Asterisk 13.14.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.14.0:rc1
  • Digium Asterisk 13.14.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:13.14.0:rc2
  • Digium Asterisk 13.14.1
    cpe:2.3:a:digium:asterisk:13.14.1
  • Digium Asterisk 13.15.0
    cpe:2.3:a:digium:asterisk:13.15.0
  • Digium Asterisk 13.15.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.15.0:rc1
  • Digium Asterisk 13.15.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:13.15.0:rc2
  • Digium Asterisk 13.15.0 Release Candidate 3
    cpe:2.3:a:digium:asterisk:13.15.0:rc3
  • Digium Asterisk 13.15.1
    cpe:2.3:a:digium:asterisk:13.15.1
  • Digium Asterisk 13.16.0
    cpe:2.3:a:digium:asterisk:13.16.0
  • Digium Asterisk 13.16.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.16.0:rc1
  • Digium Asterisk 13.16.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:13.16.0:rc2
  • Digium Asterisk 13.17.0
    cpe:2.3:a:digium:asterisk:13.17.0
  • Digium Asterisk 13.17.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:13.17.0:rc1
  • Digium Asterisk 14.0.0
    cpe:2.3:a:digium:asterisk:14.0.0
  • Digium Asterisk 14.0.0 Beta 1
    cpe:2.3:a:digium:asterisk:14.0.0:beta1
  • Digium Asterisk 14.0.0 Beta 2
    cpe:2.3:a:digium:asterisk:14.0.0:beta2
  • Digium Asterisk 14.0.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:14.0.0:rc1
  • Digium Asterisk 14.0.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:14.0.0:rc2
  • Digium Asterisk 14.0.1
    cpe:2.3:a:digium:asterisk:14.0.1
  • Digium Asterisk 14.0.2
    cpe:2.3:a:digium:asterisk:14.0.2
  • Digium Asterisk 14.01
    cpe:2.3:a:digium:asterisk:14.01
  • Digium Asterisk 14.1.0
    cpe:2.3:a:digium:asterisk:14.1.0
  • Digium Asterisk 14.1.1
    cpe:2.3:a:digium:asterisk:14.1.1
  • Digium Asterisk 14.1.2
    cpe:2.3:a:digium:asterisk:14.1.2
  • Digium Asterisk 14.02
    cpe:2.3:a:digium:asterisk:14.02
  • Digium Asterisk 14.2.0
    cpe:2.3:a:digium:asterisk:14.2.0
  • Digium Asterisk 14.2.1
    cpe:2.3:a:digium:asterisk:14.2.1
  • Digium Asterisk 14.3.0
    cpe:2.3:a:digium:asterisk:14.3.0
  • Digium Asterisk 14.3.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:14.3.0:rc1
  • Digium Asterisk 14.3.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:14.3.0:rc2
  • Digium Asterisk 14.3.1
    cpe:2.3:a:digium:asterisk:14.3.1
  • Digium Asterisk 14.4.0
    cpe:2.3:a:digium:asterisk:14.4.0
  • Digium Asterisk 14.4.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:14.4.0:rc1
  • Digium Asterisk 14.4.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:14.4.0:rc2
  • Digium Asterisk 14.4.0 Release Candidate 3
    cpe:2.3:a:digium:asterisk:14.4.0:rc3
  • Digium Asterisk 14.4.1
    cpe:2.3:a:digium:asterisk:14.4.1
  • Digium Asterisk 14.5.0
    cpe:2.3:a:digium:asterisk:14.5.0
  • Digium Asterisk 14.5.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:14.5.0:rc1
  • Digium Asterisk 14.5.0 Release Candidate 2
    cpe:2.3:a:digium:asterisk:14.5.0:rc2
  • Digium Asterisk 14.6.0
    cpe:2.3:a:digium:asterisk:14.6.0
  • Digium Asterisk 14.6.0 Release Candidate 1
    cpe:2.3:a:digium:asterisk:14.6.0:rc1
  • cpe:2.3:a:digium:certified_asterisk:13.13.0
    cpe:2.3:a:digium:certified_asterisk:13.13.0
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc1
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc1
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc2
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc2
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc3
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc3
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc4
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc4
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert2
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert2
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert3
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert3
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert4
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert4
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert5
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert5
  • cpe:2.3:a:digium:certified_asterisk:13.13.0:cert6
    cpe:2.3:a:digium:certified_asterisk:13.13.0:cert6
CVSS
Base: 4.3
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
nessus via4
  • NASL family Misc.
    NASL id ASTERISK_AST_2017_009-011.NASL
    description According to its SIP banner, the version of Asterisk running on the remote host is 13.x prior to 13.18.1, 14.x prior to 14.7.1, 15.x prior to 15.1.1, or 13.13 prior to 13.13-cert7. It is therefore, affected by multiple vulnerabilities as described in AST-2017-009, AST-2017-010, and AST-2017-011. Also note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.
    last seen 2019-02-21
    modified 2018-06-29
    plugin id 104658
    published 2017-11-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104658
    title Asterisk 13.x < 13.18.1 / 14.x < 14.7.1 / 15.x < 15.1.1 / 13.13 < 13.13-cert7 Multiple Vulnerabilities (AST-2017-009 - AST-2017-011)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201811-11.NASL
    description The remote host is affected by the vulnerability described in GLSA-201811-11 (Asterisk: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in Asterisk. Please review the referenced CVE identifiers for details. Impact : A remote attacker could cause a Denial of Service condition or conduct information gathering. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-11-26
    plugin id 119131
    published 2018-11-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=119131
    title GLSA-201811-11 : Asterisk: Multiple vulnerabilities
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-4076.NASL
    description Multiple vulnerabilities have been discovered in Asterisk, an open source PBX and telephony toolkit, which may result in denial of service, information disclosure and potentially the execution of arbitrary code.
    last seen 2019-02-21
    modified 2018-11-13
    plugin id 105498
    published 2018-01-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105498
    title Debian DSA-4076-1 : asterisk - security update
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_BE261737C53511E78DA5001999F8D30B.NASL
    description The Asterisk project reports : A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. This then leads to file descriptors and RTP ports being leaked as well.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 104491
    published 2017-11-10
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104491
    title FreeBSD : asterisk -- Memory/File Descriptor/RTP leak in pjsip session resource (be261737-c535-11e7-8da5-001999f8d30b)
refmap via4
bid 101765
confirm
debian DSA-4076
gentoo GLSA-201811-11
Last major update 08-11-2017 - 19:29
Published 08-11-2017 - 19:29
Last modified 25-11-2018 - 06:29
Back to Top