# CVE-2018-7247: Memory corruption in n/a

> A buffer overflow in Leptonica's HTML viewer allows attackers to execute arbitrary code via unsanitized input.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Feb 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-7247, GHSA-29q2-994c-m8hr, UBUNTU-CVE-2018-7247, USN-5143-1

## What is CVE-2018-7247?

CVE-2018-7247 is a critical memory corruption vulnerability in n/a, published on 19 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in pixHtmlViewer in prog/htmlviewer.c in Leptonica before 1.75.3. Unsanitized input (rootname) can overflow a buffer, leading potentially to arbitrary code execution or possibly unspecified other impact.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Leptonica Leptonica.

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

Upgrade to a fixed version.

## Is CVE-2018-7247 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7442](https://insights.sbomify.com/CVE-2018-7442/): Path traversal in n/a (critical 9.1)
- [CVE-2018-7441](https://insights.sbomify.com/CVE-2018-7441/): Race condition in n/a (high 7.0)
- [CVE-2017-18196](https://insights.sbomify.com/CVE-2017-18196/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7247 is a critical memory corruption vulnerability in n/a, published on 19 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7247 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-2018-7247/ (Markdown: https://insights.sbomify.com/CVE-2018-7247/index.md)
```

## Sources

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

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