# CVE-2018-10921: Integer overflow in ttembed

> An integer overflow in ttembed input file processing can corrupt input files due to unchecked return codes.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5g83-qvhg-p5v8

## What is CVE-2018-10921?

CVE-2018-10921 is a medium-severity vulnerability in [UNKNOWN] ttembed, published on 2 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Certain input files may trigger an integer overflow in ttembed input file processing. This overflow could potentially lead to corruption of the input file due to a lack of checking return codes of fgetc/fputc function calls.

Weakness: CWE-190 (Integer Overflow or Wraparound), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2018-10921?

It affects 1 product.


Products: Ttembed Project Ttembed.

## How do I fix CVE-2018-10921?

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

## Is CVE-2018-10921 being exploited?

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

## Other vulnerabilities in [UNKNOWN] ttembed

- [CVE-2018-10922](https://insights.sbomify.com/CVE-2018-10922/): Denial of service in ttembed (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10921 and fix it if it is affected.

What it is: CVE-2018-10921 is a medium-severity vulnerability in [UNKNOWN] ttembed, published on 2 Aug 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-10921 in the wild and no public exploit code.

Affected product: [UNKNOWN] ttembed. 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-2018-10921/ (Markdown: https://insights.sbomify.com/CVE-2018-10921/index.md)
```

## Sources

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

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