# CVE-2022-41409: Integer overflow in n/a

> An integer overflow in pcre2test allows attackers to cause a denial of service via negative input, affecting users of the PCRE2 library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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:** 18 Jul 2023
- **Updated:** 28 Oct 2024
- **Also known as:** ALPINE-CVE-2022-41409, AZL-27500, CLEANSTART-2024-WK36293, CLSA-2026-1777308424, DEBIAN-CVE-2022-41409, ECHO-740c-f4e8-2a12, GHSA-4qfx-v7wh-3q4j, JLSEC-2026-59, OESA-2023-1482, ROOT-OS-UBUNTU-2204-CVE-2022-41409, SUSE-SU-2023:3210-1, SUSE-SU-2023:3327-1, SUSE-SU-2023:3328-1, UBUNTU-CVE-2022-41409

## What is CVE-2022-41409?

CVE-2022-41409 is a high-severity vulnerability in n/a, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pcre2` | SUSE:Linux Enterprise Micro 5.1 | All versions | 10.31-150000.3.15.1 |
| `pcre2` | SUSE:Linux Enterprise Micro 5.2 | All versions | 10.31-150000.3.15.1 |
| `pcre2` | SUSE:Linux Enterprise Micro 5.3 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | SUSE:Linux Enterprise Micro 5.4 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | SUSE:Linux Enterprise Module for Basesystem 15 SP5 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 10.34-1.13.1 |
| `pcre2` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 10.34-1.13.1 |
| `pcre2` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 10.34-1.13.1 |
| `pcre2` | SUSE:Manager Proxy 4.2 | All versions | 10.31-150000.3.15.1 |
| `pcre2` | SUSE:Manager Server 4.2 | All versions | 10.31-150000.3.15.1 |
| `pcre2` | openSUSE:Leap 15.4 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | openSUSE:Leap 15.5 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | openSUSE:Leap Micro 5.3 | All versions | 10.39-150400.4.9.1 |
| `pcre2` | openSUSE:Leap Micro 5.4 | All versions | 10.39-150400.4.9.1 |

Products: Pcre Pcre2.

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

Upgrade to a fixed version.

## Is CVE-2022-41409 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41409 exists.

## Other vulnerabilities in n/a

- [CVE-2017-8786](https://insights.sbomify.com/CVE-2017-8786/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8399](https://insights.sbomify.com/CVE-2017-8399/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-89161](https://insights.sbomify.com/CVE-2026-89161/): Use after free in PCRE2 (high 7.4)
- [CVE-2025-58050](https://insights.sbomify.com/CVE-2025-58050/): PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS (medium 6.9)
- [CVE-2026-89158](https://insights.sbomify.com/CVE-2026-89158/): Integer overflow in PCRE2 (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-41409 is a high-severity vulnerability in n/a, published on 18 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-41409 exists.

Affected product: n/a. 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-41409/ (Markdown: https://insights.sbomify.com/CVE-2022-41409/index.md)
```

## Sources

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

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