CVE-2017-7244

The _pcre32_xclass function in pcre_xclass.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (invalid memory read) via a crafted file.

Published: 2017-03-23 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-7244 is rated Moderate Risk (45.1/100): CVSS Medium severity, with medium exploitation likelihood (EPSS 0.53%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-7244

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-17 0.76% 0.53% -0.24%
2 2025-11-21 0.24% 0.76% +0.52%
3 2025-11-18 — 0.24% —

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-7244

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.5 3.0 MEDIUM
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2017-7244

OS Trackers for CVE-2017-7244

vendor priority summary link
debian not yet assigned CVE-2017-7244 not yet assigned priority: Debian including 1 source packages (pcre3), 2 status rows across 2 suites (bookworm, bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2017-7244
gentoo normal CVE-2017-7244: 1 GLSA(s) (201710-25), 1 atom(s) (dev-libs/libpcre); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-7244
redhat low — https://access.redhat.com/security/cve/CVE-2017-7244
suse medium CVE-2017-7244 severity moderate: SUSE including 296 source package names (24.324:libpcre1-8.45-8.7.1, 26.374:libpcre1-8.45-8.7.1, …), 733 product×package rows across 110 product lines (Container suse/ltss/sle12.5/sles12sp5, Container suse/sles12sp3, … (110 product lines)): Fixed 271, Known Affected 231, Known Not Affected 231. https://www.suse.com/security/cve/CVE-2017-7244/
ubuntu low CVE-2017-7244 low priority: Ubuntu including 1 source packages (pcre3), 17 status rows across 17 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, precise, trusty, upstream, xenial, yakkety, zesty): not-affected 14, released 2, ignored 1. https://ubuntu.com/security/CVE-2017-7244

Affected software / configurations for CVE-2017-7244

Vendor Product Version Raw CPE
pcre pcre 8.40 cpe:2.3:a:pcre:pcre:8.40:*:*:*:*:*:*:*

References for CVE-2017-7244

cvelogic Threat Intelligence