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

> Mismatched memory management routines in the dilawar sound library allow attackers to cause memory corruption, potentially leading to code execution or crashes.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** No
- **Published:** 5 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c2p4-mhp2-gh73

## What is CVE-2018-14948?

CVE-2018-14948 is a high-severity memory corruption vulnerability in n/a, published on 5 Aug 2018. 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

An issue has been found in dilawar sound through 2017-11-27. The end of openWavFile in wav-file.cc has Mismatched Memory Management Routines (operator new [] versus operator delete).

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

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

It affects 1 product.


Products: Sound Project Sound.

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

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

## Is CVE-2018-14948 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14948 is a high-severity memory corruption vulnerability in n/a, published on 5 Aug 2018. 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-2018-14948 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-14948/ (Markdown: https://insights.sbomify.com/CVE-2018-14948/index.md)
```

## Sources

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

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