# CVE-2022-42969: Denial of service in n/a

> Remote attackers could cause denial of service in the Python py library via crafted Subversion data, though the vulnerability is disputed as unreproducible.

- **Severity:** Medium 5.3 (`CVSS:3.1/AC:L/AV:N/A:L/C:N/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2022
- **Updated:** 14 May 2025
- **Also known as:** CLSA-2026-1771978234, DEBIAN-CVE-2022-42969, MGASA-2025-0289, SUSE-SU-2023:0161-1, SUSE-SU-2023:0395-1, SUSE-SU-2023:0681-1, openSUSE-SU-2024:13211-1

## What is CVE-2022-42969?

CVE-2022-42969 is a medium-severity denial of service vulnerability in n/a, published on 16 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The py library through 1.11.0 for Python allows remote attackers to conduct a ReDoS (Regular expression Denial of Service) attack via a Subversion repository with crafted info data, because the InfoSvnCommand argument is mishandled. Note: This has been disputed by multiple third parties as not being reproduceable and they argue this is not a valid vulnerability.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-py` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | SUSE:Linux Enterprise Module for Basesystem 15 SP4 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 1.8.1-11.15.2 |
| `python-py` | SUSE:Linux Enterprise Module for Public Cloud 12 | All versions | 1.8.1-11.18.1 |
| `python-py` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.8.1-11.15.2 |
| `python-py` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 1.8.1-11.18.1 |
| `python-py` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.8.1-11.15.2 |
| `python-py` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 1.8.1-11.18.1 |
| `python-py` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.8.1-11.15.2 |
| `python-py` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 1.8.1-11.18.1 |
| `python-py` | openSUSE:Leap 15.4 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | openSUSE:Leap Micro 5.2 | All versions | 1.10.0-150100.5.12.1 |
| `python-py` | openSUSE:Leap Micro 5.3 | All versions | 1.10.0-150100.5.12.1 |

Products: Pytest Py.

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

Apply the vendor's patch.

## Is CVE-2022-42969 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-42969 is a medium-severity denial of service vulnerability in n/a, published on 16 Oct 2022. 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-42969 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-42969/ (Markdown: https://insights.sbomify.com/CVE-2022-42969/index.md)
```

## Sources

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

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