CVE-2016-9938
Last modified
CVE-2016-9938 is a vulnerability of currently unknown severity. An issue was discovered in Asterisk Open Source 11.x before 11.25.1, 13.x before 13.13.1, and 14.x before 14.2.1 and Certified Asterisk 11.x before 11.6-cert16 and 13.x before 13.8-cert4. The chan_sip channel driver has a liberal definition for whitespace when attempting to strip the content between a SIP header name and a colon character. EPSS estimates a 3.43% chance of exploitation in the next 30 days.
Description
An issue was discovered in Asterisk Open Source 11.x before 11.25.1, 13.x before 13.13.1, and 14.x before 14.2.1 and Certified Asterisk 11.x before 11.6-cert16 and 13.x before 13.8-cert4. The chan_sip channel driver has a liberal definition for whitespace when attempting to strip the content between a SIP header name and a colon character. Rather than following RFC 3261 and stripping only spaces and horizontal tabs, Asterisk treats any non-printable ASCII character as if it were whitespace. This means that headers such as Contact\x01: will be seen as a valid Contact header. This mostly does not pose a problem until Asterisk is placed in tandem with an authenticating SIP proxy. In such a case, a crafty combination of valid and invalid To headers can cause a proxy to allow an INVITE request into Asterisk without authentication since it believes the request is an in-dialog request. However, because of the bug described above, the request will look like an out-of-dialog request to Asterisk. Asterisk will then process the request as a new call. The result is that Asterisk can process calls from unvetted sources without any authentication. If you do not use a proxy for authentication, then this issue does not affect you. If your proxy is dialog-aware (meaning that the proxy keeps track of what dialogs are currently valid), then this issue does not affect you. If you use chan_pjsip instead of chan_sip, then this issue does not affect you.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Digium | Asterisk | 11.0.0 | — |
| Digium | Asterisk | 11.0.1 | — |
| Digium | Asterisk | 11.0.2 | — |
| Digium | Asterisk | 11.1.0 | — |
| Digium | Asterisk | 11.1.1 | — |
| Digium | Asterisk | 11.1.2 | — |
| Digium | Asterisk | 11.2.0 | — |
| Digium | Asterisk | 11.2.1 | — |
| Digium | Asterisk | 11.2.2 | — |
| Digium | Asterisk | 11.3.0 | — |
| Digium | Asterisk | 11.4.0 | — |
| Digium | Asterisk | 11.5.0 | — |
| Digium | Asterisk | 11.5.1 | — |
| Digium | Asterisk | 11.6.0 | — |
| Digium | Asterisk | 11.6.1 | — |
| Digium | Asterisk | 11.7.0 | — |
| Digium | Asterisk | 11.8.0 | — |
| Digium | Asterisk | 11.8.1 | — |
| Digium | Asterisk | 11.9.0 | — |
| Digium | Asterisk | 11.10.0 | — |
| Digium | Asterisk | 11.10.1 | — |
| Digium | Asterisk | 11.10.2 | — |
| Digium | Asterisk | 11.11.0 | — |
| Digium | Asterisk | 11.12.0 | — |
| Digium | Asterisk | 11.12.1 | — |
| Digium | Asterisk | 11.13.0 | — |
| Digium | Asterisk | 11.13.1 | — |
| Digium | Asterisk | 11.14.0 | — |
| Digium | Asterisk | 11.14.1 | — |
| Digium | Asterisk | 11.14.2 | — |
| Digium | Asterisk | 11.15.0 | — |
| Digium | Asterisk | 11.15.1 | — |
| Digium | Asterisk | 11.16.0 | — |
| Digium | Asterisk | 11.17.0 | — |
| Digium | Asterisk | 11.17.1 | — |
| Digium | Asterisk | 11.18.0 | — |
| Digium | Asterisk | 11.19.0 | — |
| Digium | Asterisk | 11.20.0 | — |
| Digium | Asterisk | 11.21.0 | — |
| Digium | Asterisk | 11.21.1 | — |
| Digium | Asterisk | 11.21.2 | — |
| Digium | Asterisk | 11.22.0 | — |
| Digium | Asterisk | 11.23.0 | — |
| Digium | Asterisk | 11.23.1 | — |
| Digium | Asterisk | 11.24.0 | — |
| Digium | Asterisk | 11.24.1 | — |
| Digium | Asterisk | 11.25.0 | — |
| Digium | Asterisk | 13.0.0 | — |
| Digium | Asterisk | 13.0.1 | — |
| Digium | Asterisk | 13.0.2 | — |
Showing 50 of 91 affected configurations. See NVD for the full list.
References
- http://downloads.asterisk.org/pub/security/AST-2016-009.htmlMitigation, Vendor Advisory
- http://www.securityfocus.com/bid/94789Third Party Advisory, VDB Entry
- http://downloads.asterisk.org/pub/security/AST-2016-009.htmlMitigation, Vendor Advisory
- http://www.securityfocus.com/bid/94789Third Party Advisory, VDB Entry
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2016-9938?
How severe is CVE-2016-9938?
How do I fix CVE-2016-9938?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2016
- CVE-2016-9932CMPXCHG8B emulation in Xen 3.3.x through 4.7.x on x86 system…
- CVE-2016-9933Stack consumption vulnerability in the gdImageFillToBorder f…
- CVE-2016-9934ext/wddx/wddx.c in PHP before 5.6.28 and 7.x before 7.0.13 a…
- CVE-2016-9935The php_wddx_push_element function in ext/wddx/wddx.c in PHP…
- CVE-2016-9936The unserialize implementation in ext/standard/var.c in PHP …
- CVE-2016-9937An issue was discovered in Asterisk Open Source 13.12.x and …
- CVE-2016-9939Crypto++ (aka cryptopp and libcrypto++) 5.6.4 contained a bu…
- CVE-2016-9941Heap-based buffer overflow in rfbproto.c in LibVNCClient in …
- CVE-2016-9942Heap-based buffer overflow in ultra.c in LibVNCClient in Lib…
- CVE-2016-9949An issue was discovered in Apport before 2.20.4. In apport/u…
- CVE-2016-9950An issue was discovered in Apport before 2.20.4. There is a …
- CVE-2016-9951An issue was discovered in Apport before 2.20.4. A malicious…
Are you affected by CVE-2016-9938?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
