Heap-buffer-overflow in _cmsWriteXYZNumber in lcms

lcms Updated 02 Oct 2025

Summary

27/07/2022
MEDIUM
Yes i
Medium
Not published

OSV-2022-639: Heap-buffer-overflow in _cmsWriteXYZNumber. Affects lcms versions >= 1394d740d96886b501e0ad04fe926a72eca3f01c, < 77758b7f815f4ced91e088ce855b31c90ad0a406. Fixed in 77758b7f815f4ced91e088ce855b31c90ad0a406. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

lcms is an open-source package that provides a library for managing color profiles. It is commonly used in image processing and color management applications. The package offers various functionalities for color space conversions, profile manipulation, and color correction. However, a vulnerability has been discovered in the _cmsWriteXYZNumber function of lcms, which can lead to a heap-buffer-overflow read of 8 bytes.

Vulnerability Detail

The vulnerability in lcms arises from a heap-buffer-overflow read of 8 bytes in the _cmsWriteXYZNumber function. This issue can be triggered when processing certain viewing conditions data. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The vulnerability has a medium severity rating.

How To Fix

Minimum fixed version

77758b7f815f4ced91e088ce855b31c90ad0a406

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

There is currently no known workaround for this vulnerability. It is advised to apply the fix by updating the lcms package to a patched version.

Conclusion

In conclusion, the lcms package is vulnerable to a heap-buffer-overflow read of 8 bytes in the _cmsWriteXYZNumber function. This vulnerability can be mitigated by updating the package to a version that includes the fix. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for lcms →

Share this vulnerability

FAQ

lcms is an open-source package that provides a library for managing color profiles in image processing and color management applications.

This vulnerability can potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.

To fix this vulnerability, update the lcms package to a version that includes the fix.

No, there is currently no known workaround for this vulnerability.

You can find more information about this vulnerability in the OSS-Fuzz report: [link to report].

Related vulnerabilities

Recent vulnerabilities recorded for lcms.

How To Fix

Minimum fixed version

77758b7f815f4ced91e088ce855b31c90ad0a406

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