# CVE-2018-14326: Integer overflow in n/a

> An integer overflow in MP4v2 library allows attackers to cause memory corruption, potentially leading to code execution or denial of service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h65m-rp7h-3qgc, UBUNTU-CVE-2018-14326

## What is CVE-2018-14326?

CVE-2018-14326 is a high-severity vulnerability in n/a, published on 16 Jul 2018. 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

In MP4v2 2.0.0, there is an integer overflow (with resultant memory corruption) when resizing MP4Array for the ftyp atom in mp4array.h.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Techsmith Mp4v2.

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

Upgrade to a fixed version.

## Is CVE-2018-14326 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-14403](https://insights.sbomify.com/CVE-2018-14403/): Memory corruption in n/a (critical 9.8)
- [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)

## Fix prompt for AI coding agents

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

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

## Sources

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

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