# CVE-2018-14072: Denial of service in n/a

> A memory leak in the libsixel library allows attackers to cause a denial of service via crafted Sixel images.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-14072, GHSA-m9v8-fhhm-gqcc, UBUNTU-CVE-2018-14072

## What is CVE-2018-14072?

CVE-2018-14072 is a high-severity denial of service vulnerability in n/a, published on 15 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libsixel 1.8.1 has a memory leak in sixel_decoder_decode in decoder.c, image_buffer_resize in fromsixel.c, and sixel_decode_raw in fromsixel.c.

Weakness: CWE-772 (Missing Release of Resource after Effective Lifetime)

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

It affects 1 product.


Products: Saitoha Libsixel.

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

Upgrade to a fixed version.

## Is CVE-2018-14072 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19635](https://insights.sbomify.com/CVE-2019-19635/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-19636](https://insights.sbomify.com/CVE-2019-19636/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-19637](https://insights.sbomify.com/CVE-2019-19637/): Integer overflow in n/a (critical 9.8)
- [CVE-2019-19638](https://insights.sbomify.com/CVE-2019-19638/): Integer overflow in n/a (critical 9.8)
- [CVE-2022-27044](https://insights.sbomify.com/CVE-2022-27044/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14072 is a high-severity denial of service vulnerability in n/a, published on 15 Jul 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-14072 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-14072/ (Markdown: https://insights.sbomify.com/CVE-2018-14072/index.md)
```

## Sources

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

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