# CVE-2024-35333: Memory corruption in n/a

> A stack buffer overflow in html2xhtml allows attackers to execute arbitrary code or cause denial of service via crafted input.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-35333?

CVE-2024-35333 is a high-severity memory corruption vulnerability in n/a, published on 29 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-buffer-overflow vulnerability exists in the read_charset_decl function of html2xhtml 1.3. This vulnerability occurs due to improper bounds checking when copying data into a fixed-size stack buffer. An attacker can exploit this vulnerability by providing a specially crafted input to the vulnerable function, causing a buffer overflow and potentially leading to arbitrary code execution, denial of service, or data corruption.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2024-35333?


## How do I fix CVE-2024-35333?

No fix has been published for CVE-2024-35333 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-35333 being exploited?

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

Public exploit code:

- https://github.com/momo1239/CVE-2024-35333 (github_poc): https://github.com/momo1239/CVE-2024-35333

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35333 and fix it if it is affected.

What it is: CVE-2024-35333 is a high-severity memory corruption vulnerability in n/a, published on 29 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35333 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-2024-35333/ (Markdown: https://insights.sbomify.com/CVE-2024-35333/index.md)
```

## Sources

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

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