CVE-2017-16671
Last modified
CVE-2017-16671 is a vulnerability of currently unknown severity. 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. EPSS estimates a 3.34% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Digium | Asterisk | >= 13.0.0, < 13.18.1 |
| Digium | Asterisk | >= 14.0.0, < 14.7.1 |
| Digium | Asterisk | >= 15.0.0, < 15.1.1 |
| Digium | Certified Asterisk | 13.13.0 |
References
- http://downloads.digium.com/pub/security/AST-2017-010.htmlVendor Advisory
- http://www.securityfocus.com/bid/101760Third Party Advisory, VDB Entry
- https://issues.asterisk.org/jira/browse/ASTERISK-27337Issue Tracking, Vendor Advisory
- http://downloads.digium.com/pub/security/AST-2017-010.htmlVendor Advisory
- http://www.securityfocus.com/bid/101760Third Party Advisory, VDB Entry
- https://issues.asterisk.org/jira/browse/ASTERISK-27337Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-16671?
How severe is CVE-2017-16671?
How do I fix CVE-2017-16671?
Are you affected by CVE-2017-16671?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST