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.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| http://www.securityfocus.com/bid/101760 | third party advisory vdb entry |
| http://downloads.digium.com/pub/security/AST-2017-010.html | vendor advisory |
| https://security.gentoo.org/glsa/201811-11 | vendor advisory |
| https://www.debian.org/security/2017/dsa-4076 | vendor advisory |
| https://issues.asterisk.org/jira/browse/ASTERISK-27337 | vendor advisory issue tracking |