CVE-2016-3191 Memory corruption in n/a
Remote attackers can execute arbitrary code or cause denial of service via crafted regular expressions in PCRE/PCRE2 libraries.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2016-3191?
CVE-2016-3191 is a critical memory corruption vulnerability in n/a, published on 17 Mar 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The compile_branch function in pcre_compile.c in PCRE 8.x before 8.39 and pcre2_compile.c in PCRE2 before 10.22 mishandles patterns containing an (*ACCEPT) substring in conjunction with nested parentheses, which allows remote attackers to execute arbitrary code or cause a denial of service (stack-based buffer overflow) via a crafted regular expression, as demonstrated by a JavaScript RegExp object encountered by Konqueror, aka ZDI-CAN-3542.
Weakness: CWE-119
Which versions are affected by CVE-2016-3191?
It affects 2 products.
Products include Pcre Pcre, Pcre Pcre2.
How do I fix CVE-2016-3191?
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-2016-3191 being exploited?
There is no known exploitation of CVE-2016-3191 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as ALPINE-CVE-2016-3191, DEBIAN-CVE-2016-3191, DLA-441-1, GHSA-68wg-f3j9-hgmv, UBUNTU-CVE-2016-3191.