OSV-2020-2192 Heap-buffer-overflow in decompress_smooth_data

Not scored Published

A heap-buffer-overflow in the JPEG decompression logic allows attackers to cause crashes or potentially execute code via malicious images.

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 OSV-2020-2192?

OSV-2020-2192 is a memory corruption vulnerability in libjpeg-turbo, published on 26 Nov 2020. 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

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=27852

Crash type: Heap-buffer-overflow READ 2
Crash state:
decompress_smooth_data
process_data_context_main
jpeg_read_scanlines

Which versions are affected by OSV-2020-2192?

1 open source package ship an affected version, including libjpeg-turbo.

PackageAffectedFixed in
libjpeg-turbo OSS-FuzzAll versionsNone

How do I fix OSV-2020-2192?

No fix has been published for OSV-2020-2192 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 OSV-2020-2192 being exploited?

There is no known exploitation of OSV-2020-2192 in the wild and no public exploit code.

Sources

Is OSV-2020-2192 in your software?

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

Check your SBOMs for free