CVE-2024-2881

What it actually does

Rowhammer-based fault injection against the ed25519_key structure during wc_ed25519_sign_msg execution allows an attacker sharing the same physical system to corrupt cryptographic state, resulting in information disclosure and privilege escalation.

Why it matters to the business

Organizations using WolfSSL for Ed25519 operations on shared hardware face elevated risk of credential or key compromise and unauthorized access, requiring urgent patching to maintain cryptographic integrity and system isolation.

How an attack unfolds

An attacker with co-residency on the same Linux or Windows host targets the wc_ed25519_sign_msg function, uses Rowhammer to induce bit flips in the ed25519_key structure, and leverages the resulting faulty signatures to extract sensitive key material or escalate privileges.

How to fix it

Update WolfSSL to the commit 8970ff4c34034dbb3594943d11f8c9d4c5512bd5 or later; rebuild and redeploy all dependent applications; verify the updated binary no longer contains the vulnerable ed25519.c code path.

How to confirm the fix worked

Confirm the running WolfSSL library reports a version containing commit 8970ff4c34034dbb3594943d11f8c9d4c5512bd5; perform static analysis or binary diffing to ensure the Rowhammer-vulnerable ed25519_key handling has been hardened.

Typical attack path

1. Gain co-residency on the same physical host as the target WolfSSL process
2. Identify and trigger repeated calls to wc_ed25519_sign_msg
3. Perform Rowhammer fault injection against the ed25519_key memory region
4. Observe corrupted signature output to recover key material or obtain elevated access

How to detect it

Review process execution and memory access logs for repeated calls to ed25519 signing functions from untrusted co-resident processes; look for anomalous signature outputs or unexpected privilege changes following cryptographic operations.

What your security team should do

• Immediately upgrade all WolfSSL instances to the fixed commit and rebuild dependent software
• Audit environments for any Ed25519 signing workloads running on shared hardware
• Implement memory encryption or hardware-backed isolation where Rowhammer attacks are a concern
• Monitor upstream WolfSSL releases for additional hardening against fault injection