CVE-2017-16672

UnknownEPSS 4.68%

Last modified

CVE-2017-16672 is a vulnerability of currently unknown severity. An 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. A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. EPSS estimates a 4.68% chance of exploitation in the next 30 days.

Description

An 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. A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. Eventually Asterisk can run out of memory and crash.

Metrics

EPSS Probability
4.68%

90.6th 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-16672?
An 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. A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established. When this happens the session object never gets destroyed. Eventually Asterisk can run out of memory and crash.
How severe is CVE-2017-16672?
Severity scoring for CVE-2017-16672 is pending analysis. The EPSS model estimates a 4.68% probability of exploitation in the next 30 days.
How do I fix CVE-2017-16672?
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.

Are you affected by CVE-2017-16672?

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

Scan your code now

Source: NVD / NIST