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.
References
Link | Resource |
---|---|
http://downloads.digium.com/pub/security/AST-2017-010.html | Vendor Advisory |
http://www.securityfocus.com/bid/101760 | Third Party Advisory VDB Entry |
https://issues.asterisk.org/jira/browse/ASTERISK-27337 | Issue Tracking Vendor Advisory |
https://security.gentoo.org/glsa/201811-11 | |
https://www.debian.org/security/2017/dsa-4076 |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
History
No history.
Information
Published : 2017-11-09 00:29
Updated : 2024-02-04 19:29
NVD link : CVE-2017-16671
Mitre link : CVE-2017-16671
CVE.ORG link : CVE-2017-16671
JSON object : View
Products Affected
digium
- certified_asterisk
- asterisk
CWE
CWE-119
Improper Restriction of Operations within the Bounds of a Memory Buffer