OSV-2022-367 Segv on unknown address in jxl::N_SSE4::WriteToU8Stage::ProcessRow

Not scored Published

A segmentation fault in the JPEG XL library's SSE4 rendering stage can cause a denial of service when processing crafted images.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is OSV-2022-367?

OSV-2022-367 is a memory corruption vulnerability in libjxl, published on 23 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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

Crash type: Segv on unknown address
Crash state:
jxl::N_SSE4::WriteToU8Stage::ProcessRow
jxl::LowMemoryRenderPipeline::RenderRect
jxl::LowMemoryRenderPipeline::ProcessBuffers

Which versions are affected by OSV-2022-367?

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

PackageAffectedFixed in
libjxl OSS-FuzzAll versionsNone

How do I fix OSV-2022-367?

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

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

Sources

Is OSV-2022-367 in your software?

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

Check your SBOMs for free