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

> An out-of-bounds stack write in Cairo allows attackers to execute arbitrary code or cause denial of service via crafted documents.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 8 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-18064, ECHO-e239-b681-e01f, GHSA-8wp2-6325-3w3v, JLSEC-2025-13, UBUNTU-CVE-2018-18064

## What is CVE-2018-18064?

CVE-2018-18064 is a medium-severity memory corruption vulnerability in n/a, published on 8 Oct 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

cairo through 1.15.14 has an out-of-bounds stack-memory write during processing of a crafted document by WebKitGTK+ because of the interaction between cairo-rectangular-scan-converter.c (the generate and render_rows functions) and cairo-image-compositor.c (the _cairo_image_spans_and_zero function).

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

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

It affects 1 product.


Products: Cairographics Cairo.

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

Upgrade to a fixed version.

## Is CVE-2018-18064 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35492](https://insights.sbomify.com/CVE-2020-35492/): Memory corruption in cairo (high 7.8)
- [CVE-2017-9814](https://insights.sbomify.com/CVE-2017-9814/): Denial of service in n/a (high 7.5)
- [CVE-2016-3190](https://insights.sbomify.com/CVE-2016-3190/): Denial of service in n/a (high 7.5)
- [CVE-2019-6461](https://insights.sbomify.com/CVE-2019-6461/): Denial of service in n/a (medium 6.5)
- [CVE-2019-6462](https://insights.sbomify.com/CVE-2019-6462/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18064 is a medium-severity memory corruption vulnerability in n/a, published on 8 Oct 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-18064 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-18064/ (Markdown: https://insights.sbomify.com/CVE-2018-18064/index.md)
```

## Sources

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

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