CVE-2017-16671 Memory corruption in n/a
A buffer overflow in Asterisk allows attackers to write past the user field storage buffer, potentially leading to code execution or service disruption.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2017-16671?
CVE-2017-16671 is a high-severity memory corruption vulnerability in Digium Asterisk, published on 9 Nov 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-119
Which versions are affected by CVE-2017-16671?
It affects 2 products.
Products include Digium Asterisk, Digium Certified Asterisk.
How do I fix CVE-2017-16671?
Upgrade to a fixed version.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-16671 being exploited?
There is no known exploitation of CVE-2017-16671 in the wild and no public exploit code.
Other vulnerabilities in Digium Asterisk
Sources
Also known as DEBIAN-CVE-2017-16671, GHSA-6vm7-9fw2-vx89, UBUNTU-CVE-2017-16671.