OSV-2022-725 Heap-buffer-overflow in jxl::N_EMU128::WriteToU8Stage::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
Not needed
Fix
None listed

What is OSV-2022-725?

OSV-2022-725 is a memory corruption vulnerability in libjxl, published on 18 Aug 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=50295

Crash type: Heap-buffer-overflow WRITE 1
Crash state:
jxl::N_EMU128::WriteToU8Stage::ProcessRow
jxl::LowMemoryRenderPipeline::RenderRect
jxl::LowMemoryRenderPipeline::ProcessBuffers

Which versions are affected by OSV-2022-725?

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

PackageAffectedFixed in
libjxl OSS-FuzzAll versionsNone

How do I fix OSV-2022-725?

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

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

Sources

Is OSV-2022-725 in your software?

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

Check your SBOMs for free