Skip to content
Fencer Intel
critical 9.8

CVE-2017-8399 json

PCRE2 before 10.30 has an out-of-bounds write caused by a stack-based buffer overflow in pcre2_match.c, related to a "pattern with very man…

published 2017-05-01 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-17351

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

PCRE2 before 10.30 has an out-of-bounds write caused by a stack-based buffer overflow in pcre2_match.c, related to a "pattern with very many captures."

Patch / fix

  • pcre pcre2 10.30

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-8399 updated cvss 7.8

pcre2: Stack-based buffer overflow in pcre2_match.c

  • Red Hat Enterprise Linux 5 pcre Red Hat Enterprise Linux 6 pcre, glib2 Red Hat Enterprise Linux 7 pcre, glib2, pcre2, glib2-fam, pcre-tools, glib2-tests, +5 more Red Hat JBoss Enterprise Web Server 1 httpd Red Hat JBoss Enterprise Web Server 2 jbcs-httpd24, jbcs-httpd24-runtime Red Hat JBoss Web Server 3 pcre
    +1 more products
    Red Hat Software Collections rh-php56-php, rh-php70-php, rh-php56-php-gd, rh-php70-php-gd, rh-php56-php-cli, rh-php56-php-dba, +69 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.12% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.