CVE-2017-16672

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.

Published: 2017-11-09 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2017-16672 is rated Moderate Risk (54.7/100): CVSS Medium severity, with high exploitation likelihood (EPSS 4.68%, 91th percentile). Core evidence: EPSS ranks this CVE among the most likely to be exploited in the near term. Mandatory action: High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-16672

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 5.27% 4.68% -0.59%
2 2025-03-30 7.62% 5.27% -2.35%
3 2025-03-29 7.62%

Full EPSS history (11 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-16672

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.9 3.0 MEDIUM
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
2.2 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
8.6 2.9 [email protected]

Weakness enumeration for CVE-2017-16672

OS Trackers for CVE-2017-16672

vendor priority summary link
debian not yet assigned CVE-2017-16672 not yet assigned priority: Debian including 1 source packages (asterisk), 2 status rows across 2 suites (bullseye, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2017-16672
gentoo normal CVE-2017-16672: 1 GLSA(s) (201811-11), 1 atom(s) (net-misc/asterisk); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-16672
ubuntu medium CVE-2017-16672 medium priority: Ubuntu including 1 source packages (asterisk), 21 status rows across 21 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, zesty): not-affected 16, ignored 2, DNE 1, needed 1, released 1. https://ubuntu.com/security/CVE-2017-16672

Affected software / configurations for CVE-2017-16672

Vendor Product Version Raw CPE
digium asterisk >= 13.0.0, < 13.18.1 cpe:2.3:a:digium:asterisk:*:*:*:*:*:*:*:*
digium asterisk >= 14.0.0, < 14.7.1 cpe:2.3:a:digium:asterisk:*:*:*:*:*:*:*:*
digium asterisk >= 15.0.0, < 15.1.1 cpe:2.3:a:digium:asterisk:*:*:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:*:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc1:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc2:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc3:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert1_rc4:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert2:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert3:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert4:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert5:*:*:*:*:*:*
digium certified_asterisk 13.13.0 cpe:2.3:a:digium:certified_asterisk:13.13.0:cert6:*:*:*:*:*:*

References for CVE-2017-16672

cvelogic Threat Intelligence