# CVE-2015-7507: Denial of service in Libnsbmp

> Attackers can cause a denial of service via crafted BMP files in Libnsbmp, requiring library updates to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 18 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-7507, GHSA-5j2v-4h3v-gg93

## What is CVE-2015-7507?

CVE-2015-7507 is a high-severity denial of service vulnerability in Libnsbmp, published on 18 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libnsbmp.c in Libnsbmp 0.1.2 allows context-dependent attackers to cause a denial of service (out-of-bounds read) via a crafted color table to the (1) bmp_decode_rgb or (2) bmp_decode_rle function.

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

## Which versions are affected by CVE-2015-7507?

It affects 1 product.


Products: Netsurf-Browser Libnsbmp.

## How do I fix CVE-2015-7507?

Upgrade to a fixed version.

## Is CVE-2015-7507 being exploited?

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

## Other vulnerabilities in Libnsbmp

- [CVE-2015-7508](https://insights.sbomify.com/CVE-2015-7508/): Memory corruption in Libnsbmp (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-7507 and fix it if it is affected.

What it is: CVE-2015-7507 is a high-severity denial of service vulnerability in Libnsbmp, published on 18 Feb 2020. 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-2015-7507 in the wild and no public exploit code.

Affected product: Libnsbmp. 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-2015-7507/ (Markdown: https://insights.sbomify.com/CVE-2015-7507/index.md)
```

## Sources

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

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