CVE-2016-3191Not scoredCWE-119

CVE-2016-3191: Pcre vulnerability

Pcre

Vendor fix available · Affected: Pcre · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

8.4%probability of exploitation in the next 30 days

95th percentile

050100

Higher than 95% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Memory Buffer Bounds · Memory Corruption
Vendor: Pcre
Published: March 2016
Band: Possible (1 to 10%), March 2016

CoverageNo articles yet

No CyberSIXT article names CVE-2016-3191 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

1 more reference is in the CVE record.