cve.bz

CVE-2024-40640 matrix-org vodozemac: Observable Timing Discrepancy

2.9 lowEPSS 0.2%Fix available

Low (2.9) in matrix-org vodozemac. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in vodozemac 0.7.0.

On this page
vodozemac is an open source implementation of Olm and Megolm in pure Rust. Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and `PkDecryption` Ed25519 secret keys. This flaw might allow an attacker to infer some information about the secret key material through a side-channel attack. The use of a non-constant time base64 implementation might allow an attacker to observe timing variations in the encoding and decoding operations of the secret key material. This could potentially provide insights into the underlying secret key material. The impact of this vulnerability is considered low because exploiting the attacker is required to have access to high precision timing measurements, as well as repeated access to the base64 encoding or decoding processes. Additionally, the estimated leakage amount is bounded and low according to the referenced paper. This has been patched in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272 which has been included in release version 0.7.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Severity

CVSS 3.1

2.9 low
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-07-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-208 Observable Timing Discrepancy
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • vodozemac (crates.io): fixed in 0.7.0

Ask an AI about this CVE

Show the promptExplain CVE-2024-40640 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-40640?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-40640?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-40640 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
matrix-org vodozemac< 0.7.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-j8cm-g7r6-hfpqcrates.iovodozemac<0.7.00.7.0
RUSTSEC-2024-0354crates.iovodozemac>=0.0.0-0 <0.7.00.7.0

Attack patterns (CAPEC)

  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON