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

> A heap-based buffer over-read in libsixel allows attackers to cause a denial of service via crafted image files.

- **Severity:** Medium 5.5 (`CVSS:3.0/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:** Yes
- **Published:** 30 Nov 2018
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-19759, GHSA-38x5-vg2x-7hw6, UBUNTU-CVE-2018-19759

## What is CVE-2018-19759?

CVE-2018-19759 is a medium-severity memory corruption vulnerability in n/a, published on 30 Nov 2018. 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

There is a heap-based buffer over-read at stb_image_write.h (function: stbi_write_png_to_mem) in libsixel 1.8.2 that will cause a denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Saitoha Libsixel.

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

Upgrade to a fixed version.

## Is CVE-2018-19759 being exploited?

There is no known exploitation of CVE-2018-19759 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-19759 and fix it if it is affected.

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

## Sources

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

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