CVE-2017-2811 Memory corruption in Kakadu SDK

High 8.8 Published Updated

A specially crafted JPEG 2000 file can trigger an out-of-bounds write in the Kakadu SDK, allowing attackers to execute arbitrary code.

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
None listed

What is CVE-2017-2811?

CVE-2017-2811 is a high-severity memory corruption vulnerability in Kakadu SDK, published on 24 Apr 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

A code execution vulnerability exists in the Kakadu SDK 7.9's parsing of compressed JPEG 2000 images. A specially crafted JPEG 2000 file can be read by the program, and can lead to an out of bounds write causing an exploitable condition to arise.

Weakness: CWE-787

Which versions are affected by CVE-2017-2811?

It affects 1 product.

Products include Kakadusoftware Kakadu Sdk.

How do I fix CVE-2017-2811?

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

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2017-2811 being exploited?

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

Sources

Also known as GHSA-qj5p-vmvr-x7qq.

Is CVE-2017-2811 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free