vodozemac
An implementation of Olm and Megolm in pure Rust.
View on Github
Activity
- Latest release
- 3d ago
- Total releases
- 13
- Cadence
- ~4 months
- Last 12 months
- 2
Reach
- Stars
- 397
Details
- License
- Apache-2.0
- First release
- Dec 16, 2021
| Version | Released | |
|---|---|---|
0.11.0
minor
|
0.11.0
minor
Dependencies (30)
+ 22 more
Changelog
Compare changes
|
|
0.10.0
unknown
|
0.10.0
unknown
Dependencies (29)
+ 21 more
Changelog
Compare changes
|
|
0.9.0
unknown
|
0.9.0
unknown
Dependencies (27)
+ 19 more
Changelog
Compare changes
|
|
0.8.1
unknown
|
0.8.1
unknown
Dependencies (27)
+ 19 more
Changelog
Compare changes
|
|
0.8.0
unknown
|
0.8.0
unknown
Dependencies (27)
+ 19 more
Changelog
Compare changes
|
|
0.7.0
unknown
|
0.7.0
unknown
Dependencies (28)
+ 20 more
Changelog
Compare changes
|
|
0.6.0
unknown
1 CVE
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.6.0
unknown
Dependencies (25)
+ 17 more
Changelog
Compare changes
|
|
0.5.1
unknown
2 CVEs
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2024-34063
GHSA-c3hm-hxwf-g5c6
RUSTSEC-2024-0342
May 03, 2024
vodozemac has degraded secret zeroization capabilities
2.5
/ 10
Low
Local
High
Low
None
Unchanged
Low
None
None
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. ImpactThe 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. PatchesThe patch is in commit https://github.com/matrix-org/vodozemac/pull/130/commits/297548cad4016ce448c4b5007c54db7ee39489d9. WorkaroundsNone. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.6.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.5.1
unknown
Dependencies (25)
+ 17 more
Changelog
Compare changes
|
|
0.5.0
unknown
2 CVEs
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2024-34063
GHSA-c3hm-hxwf-g5c6
RUSTSEC-2024-0342
May 03, 2024
vodozemac has degraded secret zeroization capabilities
2.5
/ 10
Low
Local
High
Low
None
Unchanged
Low
None
None
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. ImpactThe 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. PatchesThe patch is in commit https://github.com/matrix-org/vodozemac/pull/130/commits/297548cad4016ce448c4b5007c54db7ee39489d9. WorkaroundsNone. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.6.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.5.0
unknown
Dependencies (25)
+ 17 more
Changelog
Compare changes
|
|
0.4.0
unknown
1 CVE
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.4.0
unknown
Dependencies (22)
+ 14 more
Changelog
Compare changes
|
|
0.3.0
unknown
1 CVE
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.3.0
unknown
Dependencies (21)
+ 13 more
Changelog
Compare changes
|
|
0.2.0
unknown
1 CVE
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.2.0
unknown
Dependencies (20)
+ 12 more
Changelog
Compare changes
|
|
0.1.0
unknown
1 CVE
CVE-2024-40640
GHSA-j8cm-g7r6-hfpq
RUSTSEC-2024-0354
Jul 17, 2024
vodozemac's usage of non-constant time base64 decoder could lead to leakage of secret key material
Medium
Network
High
None
None
Versions before 0.7.0 of vodozemac use a non-constant time base64 implementation for importing key material for Megolm group sessions and ImpactThe 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. PatchesThe patch is in commit 734b6c6948d4b2bdee3dd8b4efa591d93a61d272. WorkaroundsNone. ReferencesA detailed description of the precise attack can be found at https://arxiv.org/abs/2108.04600. We kindly thank Soatok for pointing out this research to us. For more informationIf you have any questions or comments about this advisory please email us at security at matrix.org. Fixed in
0.7.0
References
Updated Sep 10, 2026 · Source: OSV.dev |
0.1.0
unknown
Dependencies (16)
+ 8 more
Changelog
|