# CVE-2019-5144: Memory corruption in Kakadu Software

> A heap underflow in the Kakadu Software SDK allows remote code execution via a specially crafted JP2 file.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 12 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h7qq-9c39-h27p

## What is CVE-2019-5144?

CVE-2019-5144 is a high-severity memory corruption vulnerability in Kakadu Software, published on 12 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An exploitable heap underflow vulnerability exists in the derive_taps_and_gains function in kdu_v7ar.dll of Kakadu Software SDK 7.10.2. A specially crafted jp2 file can cause a heap overflow, which can result in remote code execution. An attacker could provide a malformed file to the victim to trigger this vulnerability.

Weakness: CWE-787 (Out-of-bounds Write), CWE-191 (Integer Underflow (Wrap or Wraparound))

## Which versions are affected by CVE-2019-5144?

It affects 1 product.


Products: Kakadusoftware Kakadu Software.

## How do I fix CVE-2019-5144?

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

## Is CVE-2019-5144 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5144 and fix it if it is affected.

What it is: CVE-2019-5144 is a high-severity memory corruption vulnerability in Kakadu Software, published on 12 Dec 2019. 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-2019-5144 in the wild and no public exploit code.

Affected product: Kakadu Software. 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-2019-5144/ (Markdown: https://insights.sbomify.com/CVE-2019-5144/index.md)
```

## Sources

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

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