# CVE-2018-18197: Denial of service in n/a

> A large heap request in libgig causes an operator new[] failure, leading to a denial of service condition for applications using the library.

- **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:** No
- **Published:** 9 Oct 2018
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2018-18197, GHSA-2wm7-g572-487q, UBUNTU-CVE-2018-18197

## What is CVE-2018-18197?

CVE-2018-18197 is a critical denial of service vulnerability in n/a, published on 9 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in libgig 4.1.0. There is an operator new[] failure (due to a big pSampleLoops heap request) in DLS::Sampler::Sampler in DLS.cpp.

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

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

It affects 1 product.


Products: Linuxsampler Libgig.

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

No fix has been published for CVE-2018-18197 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-18197 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32294](https://insights.sbomify.com/CVE-2021-32294/): Memory corruption in n/a (high 8.8)
- [CVE-2018-18193](https://insights.sbomify.com/CVE-2018-18193/): Denial of service in n/a (high 8.8)
- [CVE-2018-18194](https://insights.sbomify.com/CVE-2018-18194/): Memory corruption in n/a (high 8.8)
- [CVE-2018-18196](https://insights.sbomify.com/CVE-2018-18196/): Memory corruption in n/a (high 8.8)
- [CVE-2018-14449](https://insights.sbomify.com/CVE-2018-14449/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18197 is a critical denial of service vulnerability in n/a, published on 9 Oct 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-18197 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-18197/ (Markdown: https://insights.sbomify.com/CVE-2018-18197/index.md)
```

## Sources

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

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