CVE-2019-20454

What it is

An out-of-bounds read was discovered in PCRE before 10.34 when the pattern \X is JIT compiled and used to match specially crafted subjects in non-UTF mode. Applications that use PCRE to parse untrusted input may be vulnerable to this flaw, which would allow an attacker to crash the application. The flaw occurs in do_extuni_no_utf in pcre2_jit_compile.c.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of service disruption.

Exploit odds

1.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-02-14 14:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-11-02 18:18 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.6% in the next 30 days (EPSS).
• Severity: 7.5 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-02-14 14:15 UTC

Last modified

2026-11-02 18:18 UTC

Exploit probability

1.6% · EPSS, next 30 days

Weakness

CWE-125 · Out-of-bounds read

Record status

Modified

Affected

• Pcre pcre2 < 10.34
• Fedoraproject Fedora 31
• Splunk Universal Forwarder < 8.2.12
• Splunk Universal Forwarder < 9.0.6
• Splunk Universal Forwarder 9.1.0

Attack profile CVSS 3.1 · 7.5

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-20454.md and follow it. Check whether this project is affected by CVE-2019-20454. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge