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

> A heap-based buffer over-read in the CImg library allows attackers to cause denial of service or disclose information via a crafted BMP image.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 2 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-7638, GHSA-r2x2-928x-m223, UBUNTU-CVE-2018-7638

## What is CVE-2018-7638?

CVE-2018-7638 is a high-severity memory corruption vulnerability in n/a, published on 2 Mar 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

An issue was discovered in CImg v.220. A heap-based buffer over-read in load_bmp in CImg.h occurs when loading a crafted bmp image, a different vulnerability than CVE-2018-7588. This is in a "256 colors" case, aka case 8.

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

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

It affects 1 product.


Products: Cimg Cimg.

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

Upgrade to a fixed version.

## Is CVE-2018-7638 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-13568](https://insights.sbomify.com/CVE-2019-13568/): Memory corruption in n/a (high 8.8)
- [CVE-2023-41484](https://insights.sbomify.com/CVE-2023-41484/): Information disclosure in n/a (high 8.1)
- [CVE-2020-25693](https://insights.sbomify.com/CVE-2020-25693/): Integer overflow in CImg (high 8.1)
- [CVE-2024-26540](https://insights.sbomify.com/CVE-2024-26540/): Memory corruption in n/a (high 7.8)
- [CVE-2018-7637](https://insights.sbomify.com/CVE-2018-7637/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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