Segv on unknown address in libjxl: N_SSE4::WriteToU8Stage::ProcessRow

libjxl Updated 02 Oct 2025

Summary

23/04/2022
N/A
Yes i
Unrated
Not published

OSV-2022-367: Segv on unknown address in jxl::N_SSE4::WriteToU8Stage::ProcessRow. Affects libjxl versions >= 239aa089e1025f328f8c4df76483c8d8f20b4f3f, < a3bd8dfcb42a1ba7e77868ea626c07095ac7dc3e. Fixed in a3bd8dfcb42a1ba7e77868ea626c07095ac7dc3e. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libjxl is an open-source library for JPEG XL image compression. It provides various functionalities for encoding and decoding images in the JPEG XL format. The library is widely used in applications that require efficient image compression and decompression. However, a vulnerability has been discovered in the library that can lead to a segmentation fault (segv) when processing certain image data.

Vulnerability Detail

The vulnerability in libjxl, specifically in the N_SSE4::WriteToU8Stage::ProcessRow function, can result in a segv on an unknown address. This can occur when the library is rendering a rectangle and processing buffers. The exact cause of the segv is currently unknown. The impact of this vulnerability can range from a denial of service (crash) to potential exploitation of the segv for arbitrary code execution.

How To Fix

Minimum fixed version

a3bd8dfcb42a1ba7e77868ea626c07095ac7dc3e

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

At the moment, there is no known workaround for this vulnerability. It is recommended to apply the fix mentioned in the 'how_to_fix' section.

Conclusion

In conclusion, the libjxl library is vulnerable to a segv on an unknown address when processing certain image data. This vulnerability can have various impacts, including crashes and potential code execution. It is crucial to update to the latest version of libjxl that includes the fix to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libjxl →

Share this vulnerability

FAQ

libjxl is an open-source library for JPEG XL image compression.

The impact can range from a denial of service (crash) to potential exploitation of the segv for arbitrary code execution.

To fix this vulnerability, update to the latest version of libjxl that includes the fix.

At the moment, there is no known workaround for this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for libjxl.

How To Fix

Minimum fixed version

a3bd8dfcb42a1ba7e77868ea626c07095ac7dc3e

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback