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.
2017-11-09T00:29:00.473
2025-04-20T01:37:25.860
Deferred
CVSSv3.0: 8.8 (HIGH)
AV:N/AC:L/Au:S/C:P/I:P/A:P
8.0
6.4
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | digium | asterisk | < 13.18.1 | Yes |
Application | digium | asterisk | < 14.7.1 | Yes |
Application | digium | asterisk | < 15.1.1 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |
Application | digium | certified_asterisk | 13.13.0 | Yes |