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

> Type confusion in MP4v2 library allows out-of-bounds memory access, potentially leading to code execution or denial of service.

- **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:** Yes
- **Published:** 19 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cq9c-6m4q-fv48, UBUNTU-CVE-2018-14403

## What is CVE-2018-14403?

CVE-2018-14403 is a critical memory corruption vulnerability in n/a, published on 19 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MP4NameFirstMatches in mp4util.cpp in MP4v2 2.0.0 mishandles substrings of atom names, leading to use of an inappropriate data type for associated atoms. The resulting type confusion can cause out-of-bounds memory access.

Weakness: CWE-704 (Incorrect Type Conversion or Cast)

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

It affects 1 product.


Products: Techsmith Mp4v2.

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

Apply the vendor's patch.

## Is CVE-2018-14403 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14054](https://insights.sbomify.com/CVE-2018-14054/): Use after free in n/a (critical 9.8)
- [CVE-2018-14446](https://insights.sbomify.com/CVE-2018-14446/): Memory corruption in n/a (high 8.8)
- [CVE-2018-14379](https://insights.sbomify.com/CVE-2018-14379/): Memory corruption in n/a (high 8.8)
- [CVE-2018-14325](https://insights.sbomify.com/CVE-2018-14325/): Integer overflow in n/a (high 8.8)
- [CVE-2018-14326](https://insights.sbomify.com/CVE-2018-14326/): Integer overflow in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14403 is a critical memory corruption vulnerability in n/a, published on 19 Jul 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-14403 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-14403/ (Markdown: https://insights.sbomify.com/CVE-2018-14403/index.md)
```

## Sources

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

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