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

> A heap-based buffer overflow in sam2p allows attackers to cause denial of service or potentially execute arbitrary code via crafted BMP files.

- **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 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4jvf-74q2-q54g, UBUNTU-CVE-2018-12578

## What is CVE-2018-12578?

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

### Official description

There is a heap-based buffer overflow in bmp_compress1_row in appliers.cpp in sam2p 0.49.4 that leads to a denial of service or possibly unspecified other impact.

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

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

It affects 1 product.


Products: Sam2p Project Sam2p.

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

Upgrade to a fixed version.

## Is CVE-2018-12578 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-14636](https://insights.sbomify.com/CVE-2017-14636/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-14637](https://insights.sbomify.com/CVE-2017-14637/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-14628](https://insights.sbomify.com/CVE-2017-14628/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-14630](https://insights.sbomify.com/CVE-2017-14630/): Integer overflow in n/a (critical 9.8)
- [CVE-2017-14631](https://insights.sbomify.com/CVE-2017-14631/): Integer overflow in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12578 is a critical memory corruption vulnerability in n/a, published on 19 Jun 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-12578 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-12578/ (Markdown: https://insights.sbomify.com/CVE-2018-12578/index.md)
```

## Sources

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

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