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

> Remote attackers can cause a denial of service via a crafted gig file due to an invalid memory write in libgig.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 28 Aug 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-12953, GHSA-9rfv-x72m-w755, UBUNTU-CVE-2017-12953

## What is CVE-2017-12953?

CVE-2017-12953 is a medium-severity memory corruption vulnerability in n/a, published on 28 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The gig::Instrument::UpdateRegionKeyTable function in gig.cpp in libgig 4.0.0 allows remote attackers to cause a denial of service (invalid memory write and application crash) via a crafted gig file.

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

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

It affects 1 product.


Products: Libgig0 Libgig.

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

Upgrade to a fixed version.

## Is CVE-2017-12953 being exploited?

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

Public exploit code:

- libgig 4.0.0 (LinuxSampler) - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-12951](https://insights.sbomify.com/CVE-2017-12951/): Denial of service in n/a (medium 6.5)
- [CVE-2017-12952](https://insights.sbomify.com/CVE-2017-12952/): Null dereference in n/a (medium 6.5)
- [CVE-2017-12954](https://insights.sbomify.com/CVE-2017-12954/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-12953 is a medium-severity memory corruption vulnerability in n/a, published on 28 Aug 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-12953 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-2017-12953/ (Markdown: https://insights.sbomify.com/CVE-2017-12953/index.md)
```

## Sources

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

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