What is CVE-2024-34063?

CVE-2024-34063 is a low-severity security vulnerability in vodozemac (rust), affecting versions >= 0.5.0, < 0.6.0. It is fixed in 0.6.0.

How severe is CVE-2024-34063?

CVE-2024-34063 has a CVSS score of 2.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of vodozemac are affected by CVE-2024-34063?

vodozemac (rust) versions >= 0.5.0, < 0.6.0 is affected.

Is there a fix for CVE-2024-34063?

Yes. CVE-2024-34063 is fixed in 0.6.0. Upgrade to this version or later.

Is CVE-2024-34063 exploitable, and should I be worried?

Whether CVE-2024-34063 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 CVE-2024-34063 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 CVE-2024-34063?

Upgrade vodozemac to 0.6.0 or later.

CVE-2024-34063 in vodozemac

Q: How severe is CVE-2024-34063?

CVE-2024-34063 has a CVSS score of 2.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of vodozemac are affected by CVE-2024-34063?

vodozemac (rust) versions >= 0.5.0, < 0.6.0 is affected.

Q: Is there a fix for CVE-2024-34063?

Yes. CVE-2024-34063 is fixed in 0.6.0. Upgrade to this version or later.

Q: Is CVE-2024-34063 exploitable, and should I be worried?

Whether CVE-2024-34063 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 CVE-2024-34063 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.

Q: How do I fix CVE-2024-34063?

Upgrade vodozemac to 0.6.0 or later.

Summary

vodozemac has degraded secret zeroization capabilities

Versions 0.5.0 and 0.5.1 of vodozemac have degraded secret zeroization capabilities, due to changes in third-party cryptographic dependencies (the Dalek crates), which moved secret zeroization capabilities behind a feature flag while vodozemac disabled the default feature set.

Workarounds

None.

For more information

If you have any questions or comments about this advisory please email us at security at matrix.org.

Impact

The degraded zeroization capabilities could result in the production of more memory copies of encryption secrets and secrets could linger in memory longer than necessary. This marginally increases the risk of sensitive data exposure.

Overall, we consider the impact of this issue to be low. Although cryptographic best practices recommend the clearing of sensitive information from memory once it's no longer needed, the inherent limitations of Rust regarding absolute zeroization reduce the practical severity of this lapse.

CVE-2024-34063 has a CVSS score of 2.5 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.6.0); upgrading removes the vulnerable code path.

Affected versions

vodozemac (>= 0.5.0, < 0.6.0)

Security releases

vodozemac → 0.6.0 (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

The patch is in commit https://github.com/matrix-org/vodozemac/pull/130/commits/297548cad4016ce448c4b5007c54db7ee39489d9.

Frequently Asked Questions

What is CVE-2024-34063? CVE-2024-34063 is a low-severity security vulnerability in vodozemac (rust), affecting versions >= 0.5.0, < 0.6.0. It is fixed in 0.6.0.
How severe is CVE-2024-34063? CVE-2024-34063 has a CVSS score of 2.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of vodozemac are affected by CVE-2024-34063? vodozemac (rust) versions >= 0.5.0, < 0.6.0 is affected.
Is there a fix for CVE-2024-34063? Yes. CVE-2024-34063 is fixed in 0.6.0. Upgrade to this version or later.
Is CVE-2024-34063 exploitable, and should I be worried? Whether CVE-2024-34063 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 CVE-2024-34063 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 CVE-2024-34063? Upgrade vodozemac to 0.6.0 or later.

Other vulnerabilities in vodozemac

CVE-IDSeverityPackage summary

CVE-2024-40640Mediumvodozemac: vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material