# CVE-2017-15953: Memory corruption in n/a

> A heap-based buffer overflow in bchunk allows attackers to cause a crash or potentially execute code via a malformed CUE file.

- **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:** 28 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-15953, GHSA-c6qw-q96c-8vv4, UBUNTU-CVE-2017-15953

## What is CVE-2017-15953?

CVE-2017-15953 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 28 Oct 2017. 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

bchunk (related to BinChunker) 1.2.0 and 1.2.1 is vulnerable to a heap-based buffer overflow and crash when processing a malformed CUE (.cue) file.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-15953?

It affects 2 products.


Products: Bchunk Project Bchunk, Debian Debian Linux.

## How do I fix CVE-2017-15953?

Upgrade to a fixed version.

## Is CVE-2017-15953 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2017-15954](https://insights.sbomify.com/CVE-2017-15954/): Memory corruption in n/a (medium 5.5)
- [CVE-2017-15955](https://insights.sbomify.com/CVE-2017-15955/): Null dereference in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15953 and fix it if it is affected.

What it is: CVE-2017-15953 is a medium-severity memory corruption vulnerability in Debian Debian Linux, published on 28 Oct 2017. 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-2017-15953 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2017-15953/ (Markdown: https://insights.sbomify.com/CVE-2017-15953/index.md)
```

## Sources

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

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