# CVE-2023-34623: Denial of service in n/a

> Attackers can cause denial of service in jTidy via crafted objects with cyclic dependencies, affecting Java applications using this 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:** 14 Jun 2023
- **Updated:** 3 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-34623, GHSA-fv2r-hw24-8rxj, OESA-2026-1657, SUSE-SU-2023:3016-1, SUSE-SU-2023:3164-1, SUSE-SU-2023:3165-1, UBUNTU-CVE-2023-34623, openSUSE-SU-2024:13152-1

## What is CVE-2023-34623?

CVE-2023-34623 is a high-severity denial of service vulnerability in n/a, published on 14 Jun 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered jtidy thru r938 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2023-34623?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jtidy` | SUSE:Linux Enterprise High Performance Computing 15 SP1-LTSS | All versions | 8.0-150000.4.3.1 |
| `jtidy` | SUSE:Linux Enterprise Module for Development Tools 15 SP4 | All versions | 8.0-150200.11.7.1 |
| `jtidy` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 8.0-150200.11.7.1 |
| `jtidy` | SUSE:Linux Enterprise Real Time 15 SP3 | All versions | 8.0-150200.11.7.1 |
| `jtidy` | SUSE:Linux Enterprise Server 15 SP1-LTSS | All versions | 8.0-150000.4.3.1 |
| `jtidy` | SUSE:Linux Enterprise Server for SAP Applications 15 SP1 | All versions | 8.0-150000.4.3.1 |
| `jtidy` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 8.0-27.3.1 |
| `jtidy` | openSUSE:Leap 15.4 | All versions | 8.0-150200.11.7.1 |
| `jtidy` | openSUSE:Leap 15.5 | All versions | 8.0-150200.11.7.1 |
| `jtidy` | openSUSE:Tumbleweed | All versions | 1.0.4-1.1 |

Products: Jtidy Project Jtidy.

## How do I fix CVE-2023-34623?

Apply the vendor's patch.

## Is CVE-2023-34623 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-34623 and fix it if it is affected.

What it is: CVE-2023-34623 is a high-severity denial of service vulnerability in n/a, published on 14 Jun 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-2023-34623 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-2023-34623/ (Markdown: https://insights.sbomify.com/CVE-2023-34623/index.md)
```

## Sources

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

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