CVE-2017-16672
A memory leak occurs when an Asterisk pjsip session object is created and that call gets rejected before the session itself is fully established.
Does this matter?
Lower severity and a low EPSS score (4.68%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.0
- 5.9 MEDIUMCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 4.68% probability · 91th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-772
- Affected
- digium/asterisk · digium/certified asterisk
- Source
- cve@mitre.org
References
- http://downloads.digium.com/pub/security/AST-2017-011.htmlVendor Advisory
- http://www.securityfocus.com/bid/101765Third Party Advisory, VDB Entry
- https://issues.asterisk.org/jira/browse/ASTERISK-27345Vendor Advisory
- https://security.gentoo.org/glsa/201811-11
- https://www.debian.org/security/2017/dsa-4076
- http://downloads.digium.com/pub/security/AST-2017-011.htmlVendor Advisory
- http://www.securityfocus.com/bid/101765Third Party Advisory, VDB Entry
- https://issues.asterisk.org/jira/browse/ASTERISK-27345Vendor Advisory
- https://security.gentoo.org/glsa/201811-11
- https://www.debian.org/security/2017/dsa-4076
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.