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

> Attackers can cause a Denial of Service in epub2txt2 by submitting a crafted XML file that triggers an integer overflow.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cmrp-cwg4-4p53

## What is CVE-2022-29358?

CVE-2022-29358 is a medium-severity vulnerability in n/a, published on 24 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

epub2txt2 v2.04 was discovered to contain an integer overflow via the function bug in _parse_special_tag at sxmlc.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted XML file.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Epub2txt2 Project Epub2txt2.

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

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

## Is CVE-2022-29358 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-29358 is a medium-severity vulnerability in n/a, published on 24 May 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29358 in the wild and no public exploit code.

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-29358/ (Markdown: https://insights.sbomify.com/CVE-2022-29358/index.md)
```

## Sources

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

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