rustsec-2025-0133
Vulnerability from osv_rustsec
Published
2025-12-04 12:00
Modified
2025-12-06 07:36
Summary
Incorrect calculation on aarch64
Details
On platforms without the core::arch::aarch64::vxarq_u64 intrinsic, an unverified fallback in libcrux-intrinsics v0.0.3
passed incorrect arguments and produced wrong results. This corrupted SHA-3 digests and caused libcrux-ml-kem and
libcrux-ml-dsa to sample incorrectly, yielding incorrect shared secrets and invalid signatures.
The issue has been fixed in v0.0.4.
{
"affected": [
{
"database_specific": {
"categories": [
"crypto-failure"
],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [
"aarch64"
],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "libcrux-intrinsics",
"purl": "pkg:cargo/libcrux-intrinsics"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.4-0"
},
{
"fixed": "0.0.4"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [
"GHSA-2cgv-28vr-rv6j"
],
"database_specific": {
"license": "CC0-1.0"
},
"details": "On platforms without the `core::arch::aarch64::vxarq_u64` intrinsic, an unverified fallback in `libcrux-intrinsics` v0.0.3\npassed incorrect arguments and produced wrong results. This corrupted SHA-3 digests and caused `libcrux-ml-kem` and\n`libcrux-ml-dsa` to sample incorrectly, yielding incorrect shared secrets and invalid signatures.\n\nThe issue has been fixed in v0.0.4.",
"id": "RUSTSEC-2025-0133",
"modified": "2025-12-06T07:36:56Z",
"published": "2025-12-04T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/libcrux-intrinsics"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2025-0133.html"
},
{
"type": "REPORT",
"url": "https://github.com/cryspen/libcrux/issues/1220"
}
],
"related": [],
"severity": [],
"summary": "Incorrect calculation on aarch64"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…