# CVE-2022-1587: Memory corruption in pcre2

> An out-of-bounds read in PCRE2's JIT compiler allows attackers to cause denial of service or disclose sensitive memory contents via crafted regex.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-1587, CLEANSTART-2024-AI93387, DEBIAN-CVE-2022-1587, GHSA-jmvm-hj36-w5hc, SUSE-SU-2022:2565-1, SUSE-SU-2022:2566-1, UBUNTU-CVE-2022-1587

## What is CVE-2022-1587?

CVE-2022-1587 is a critical memory corruption vulnerability in Fedoraproject Fedora, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2022-1587?

It affects 12 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pcre2` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 10.39-150400.4.6.1 |
| `pcre2` | SUSE:Linux Enterprise Server 12 SP2-BCL | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:Linux Enterprise Server 12 SP3-BCL | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:Linux Enterprise Server 12 SP4-LTSS | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP4 | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:OpenStack Cloud 9 | All versions | 10.34-1.10.1 |
| `pcre2` | SUSE:OpenStack Cloud Crowbar 9 | All versions | 10.34-1.10.1 |
| `pcre2` | openSUSE:Leap 15.4 | All versions | 10.39-150400.4.6.1 |

Products: Fedoraproject Fedora, Netapp Active Iq Unified Manager, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware, Netapp Hci Management Node, Netapp Ontap Select Deploy Administration Utility, Netapp Solidfire, Pcre Pcre2, Redhat Enterprise Linux.

## How do I fix CVE-2022-1587?

Apply the vendor's patch.

## Is CVE-2022-1587 being exploited?

There is no known exploitation of CVE-2022-1587 in the wild and no public exploit code.

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1587 and fix it if it is affected.

What it is: CVE-2022-1587 is a critical memory corruption vulnerability in Fedoraproject Fedora, published on 16 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1587 in the wild and no public exploit code.

Affected product: Fedoraproject Fedora. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1587/ (Markdown: https://insights.sbomify.com/CVE-2022-1587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1587
- OSV: https://osv.dev/vulnerability/CVE-2022-1587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1587/
Summaries are generated and may contain mistakes; the official description above is the record.