CVE-2024-40640None▾ SunlitUsage of non-constant time base64 decoder could lead to leakage of secret key material
▾ Sunlit zone — Low / medium · no exploitation signal
impact 2.8 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Oct 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.2%
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[1].
vodozemac >= 0.0.0-0, < 0.7.0Upgrade to a patched release:
vodozemac 0.7.0Connected by shared product, vendor, weakness, or advisory.