Which versions of lzf are affected by GHSA-5M39-WX2Q-MXG3?

lzf (rust) versions < 0.3.2 is affected.

Is there a fix for GHSA-5M39-WX2Q-MXG3?

Yes. GHSA-5M39-WX2Q-MXG3 is fixed in 0.3.2. Upgrade to this version or later.

Is GHSA-5M39-WX2Q-MXG3 exploitable, and should I be worried?

Whether GHSA-5M39-WX2Q-MXG3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-5M39-WX2Q-MXG3 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-5M39-WX2Q-MXG3 in lzf

Q: What is GHSA-5M39-WX2Q-MXG3?

GHSA-5M39-WX2Q-MXG3 is a medium-severity security vulnerability in lzf (rust), affecting versions < 0.3.2. It is fixed in 0.3.2.

Q: Which versions of lzf are affected by GHSA-5M39-WX2Q-MXG3?

lzf (rust) versions < 0.3.2 is affected.

Q: Is there a fix for GHSA-5M39-WX2Q-MXG3?

Yes. GHSA-5M39-WX2Q-MXG3 is fixed in 0.3.2. Upgrade to this version or later.

Q: Is GHSA-5M39-WX2Q-MXG3 exploitable, and should I be worried?

Whether GHSA-5M39-WX2Q-MXG3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-5M39-WX2Q-MXG3 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-5M39-WX2Q-MXG3

GHSA-5M39-WX2Q-MXG3 is a medium-severity security vulnerability in lzf (rust), affecting versions < 0.3.2. It is fixed in 0.3.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Invalid use of mem::uninitialized causes use-of-uninitialized-value

The compression and decompression function used mem:uninitialized to create an array of uninitialized values, to later write values into it. This later leads to reads from uninitialized memory.

The flaw was corrected in commit b633bf265e41c60dfce3be7eac4e4dd5e18d06cf by using a heap-allocated Vec and removing out use of mem::uninitialized. The fix was released in v0.3.2 and v1.0.0

Subsequently, the crate was deprecated and its use is discouraged.

Impact

Affected versions

lzf (< 0.3.2)

Security releases

lzf → 0.3.2 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade lzf to 0.3.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-5M39-WX2Q-MXG3? GHSA-5M39-WX2Q-MXG3 is a medium-severity security vulnerability in lzf (rust), affecting versions < 0.3.2. It is fixed in 0.3.2.
Which versions of lzf are affected by GHSA-5M39-WX2Q-MXG3? lzf (rust) versions < 0.3.2 is affected.
Is there a fix for GHSA-5M39-WX2Q-MXG3? Yes. GHSA-5M39-WX2Q-MXG3 is fixed in 0.3.2. Upgrade to this version or later.
Is GHSA-5M39-WX2Q-MXG3 exploitable, and should I be worried? Whether GHSA-5M39-WX2Q-MXG3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-5M39-WX2Q-MXG3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-5M39-WX2Q-MXG3? Upgrade lzf to 0.3.2 or later.