dbcve.org
Enterprise LinuxOperating system · Redhat

CVE-2022-1587

CRITICAL · 9.1 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 10.40 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An out-of-bounds read vulnerability was discovered in the PCRE2 library in the get_recurse_data_length() function of the pcre2_jit_compile.c file. This issue affects recursions in JIT-compiled regular expressions caused by duplicate data transfers.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-125

The code reads past the end (or before the start) of a buffer, returning memory that was never meant to be exposed. Attackers use it to leak secrets like keys or to defeat memory-protection defences. Remediation is validating indices and lengths before every read.

General guidance for the out-of-bounds read class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Enterprise LinuxOperating system
Affected:= 9.0
FedoraOperating system
Affected:= 35= 36
Pcre2Application
Affected:< 10.40
Active Iq Unified ManagerApplication
Affected:all versions
Hci Management NodeApplication
Affected:all versions
Ontap Select Deploy Administration UtilityApplication
Affected:all versions
SolidfireApplication
Affected:all versions
H300s FirmwareOperating system
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.40 or later
Fixed in 10.40
Vendor patch github.com →
Recommended fix High confidence

PCRE2 version 10.40 or later

  1. 1. Identify the Linux distribution running on the system (e.g., RHEL/CentOS, Fedora, Debian)
  2. 2. For RHEL/CentOS/Enterprise Linux systems: Run 'dnf check-update' or 'yum check-update' to see available PCRE2 updates
  3. 3. For RHEL/CentOS/Enterprise Linux systems: Run 'dnf update pcre2' or 'yum update pcre2' to install the patched version (10.40 or later)
  4. 4. For Fedora systems: Run 'dnf update pcre2' to upgrade to the fixed version
  5. 5. For Debian/Ubuntu systems: Run 'apt-get update' followed by 'apt-get upgrade libpcre2-dev' or 'apt-get install --reinstall libpcre2-8'
  6. 6. After upgrading, restart any services that use PCRE2 to ensure the patched library is loaded
  7. 7. Verify the installed PCRE2 version using 'pcre2-config --version' or 'rpm -q pcre2' to confirm version 10.40 or later is installed
Caveat PCRE2 10.40 includes bug fixes and potential minor behavior changes; test regex patterns in non-production environments before deploying widely

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,550. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1587 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1587 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data