CVE-2017-16671

high-risk
Published 2017-11-09

A Buffer Overflow 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. No size checking is done when setting the user field for Party B on a CDR. Thus, it is possible for someone to use an arbitrarily large string and write past the end of the user field storage buffer. NOTE: this is different from CVE-2017-7617, which was only about the Party A buffer.

Do I need to act?

~
3.6% chance of exploitation in next 30 days
EPSS score — moderate exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
8
CVSS 8.8/10 High
NETWORK / LOW complexity

Affected Products (12)

Affected Vendors

Digium

References (10)

Vendor Advisory http://downloads.digium.com/pub/security/AST-2017-010.html
Third Party Advisory http://www.securityfocus.com/bid/101760
Issue Tracking https://issues.asterisk.org/jira/browse/ASTERISK-27337
https://security.gentoo.org/glsa/201811-11
https://www.debian.org/security/2017/dsa-4076
Vendor Advisory http://downloads.digium.com/pub/security/AST-2017-010.html
Third Party Advisory http://www.securityfocus.com/bid/101760
Issue Tracking https://issues.asterisk.org/jira/browse/ASTERISK-27337
https://security.gentoo.org/glsa/201811-11
https://www.debian.org/security/2017/dsa-4076
54
/ 100
high-risk
Severity 30/34 · Critical
Exploitability 7/34 · Low
Exposure 17/34 · Moderate