Strix
26.1K

CVE-2017-16671

UnknownEPSS 3.34%

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

EPSS Probability
3.34%

87.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
DigiumAsterisk>= 13.0.0, < 13.18.1
DigiumAsterisk>= 14.0.0, < 14.7.1
DigiumAsterisk>= 15.0.0, < 15.1.1
DigiumCertified Asterisk13.13.0

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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.
How severe is CVE-2017-16671?
Severity scoring for CVE-2017-16671 is pending analysis. The EPSS model estimates a 3.34% probability of exploitation in the next 30 days.
How do I fix CVE-2017-16671?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2017

View all 2017CVEs →

Are you affected by CVE-2017-16671?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST