OSV-2022-264 Heap-buffer-overflow in jxl::N_AVX2::BlendingStage::ProcessRow

Not scored Published

A heap-buffer-overflow in the JPEG XL library allows attackers to cause denial of service or potentially execute code via crafted 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-2022-264?

OSV-2022-264 is a memory corruption vulnerability in libvips, published on 21 Mar 2022. 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=45822

Crash type: Heap-buffer-overflow READ 4
Crash state:
jxl::N_AVX2::BlendingStage::ProcessRow
jxl::LowMemoryRenderPipeline::RenderRect
jxl::LowMemoryRenderPipeline::ProcessBuffers

Which versions are affected by OSV-2022-264?

1 open source package ship an affected version, including libvips.

PackageAffectedFixed in
libvips OSS-FuzzAll versionsNone

How do I fix OSV-2022-264?

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

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

Sources

Is OSV-2022-264 in your software?

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

Check your SBOMs for free