OSV-2022-493 Segv on unknown address in jxl::N_AVX2::XYBStage<jxl::N_AVX2::PerChannelOp<jxl::N_AVX2::Op709> >::ProcessRo

Not scored Published

A segmentation fault in the JPEG XL library's AVX2 rendering pipeline can cause a denial of service when processing 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-2022-493?

OSV-2022-493 is a memory corruption vulnerability in libvips, published on 21 Jun 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=48132

Crash type: Segv on unknown address
Crash state:
jxl::N_AVX2::XYBStage&lt;jxl::N_AVX2::PerChannelOp&lt;jxl::N_AVX2::Op709&gt; &gt;::ProcessRo
jxl::LowMemoryRenderPipeline::RenderRect
jxl::LowMemoryRenderPipeline::ProcessBuffers

Which versions are affected by OSV-2022-493?

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

PackageAffectedFixed in
libvips OSS-FuzzAll versionsNone

How do I fix OSV-2022-493?

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

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

Sources

Is OSV-2022-493 in your software?

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

Check your SBOMs for free