Buffer overflow in Digium Asterisk

CVE-2017-16671

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.

Vulnerability class: Buffer Overflow

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.8 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.033 (88.2th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 88th percentile — 88.2% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2017-16671: held from 0.033 to 0.033.

EPSS over last 30 days · oldest: 0.033 · newest: 0.033 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2017-16671?
CVE-2017-16671 is a high-severity vulnerability in Digium Asterisk, classified under Improper Restriction of Operations within the Bounds of a Memory Buffer. CVSS score: 8.8/10. Published 2017-11-09.
How severe is CVE-2017-16671?
High severity. CVSS v3 base score is 8.8 out of 10.