CVE-2024-1545 is a medium severity (CVSS 5.9) fault injection weakness in the RsaPrivateDecryption function of wolfSSL 5.6.6. An attacker who co-resides on the same system could use Rowhammer to corrupt the RSA key structure and disclose information. wolfSSL fixed it in its 5.7.0 release.
What's affected
The record names wolfSSL 5.6.6 on Linux and Windows. The wolfSSL 5.7.0 release notes list the fix as a medium item, "Fault Injection vulnerability in RsaPrivateDecryption", fixed in pull request 7167, and credit the researchers named there.
The release notes rate it Medium, matching the record's 5.9. The attacker must run code on the same physical machine as the victim process. That makes shared hosts, such as multi tenant servers and cloud instances with untrusted neighbours, the cases to think about first. The record does not say whether versions before 5.6.6 are affected.
How to check if you're exposed
Find which wolfSSL your software uses. On a Linux system with a package manager:
dpkg -l | grep -i wolfssl
rpm -qa | grep -i wolfssl
Many products link wolfSSL statically, so also check vendor notes for embedded devices and applications. Your software bill of materials is the quickest route to this answer.
To check a whole codebase at once, run the free in-browser dependency scan at gold.safeguard.sh/scan. You can also look up the CVE in the Gold directory, and use reachability analysis to see whether your code calls the affected path.
What to do now
- Find every product and package that includes wolfSSL.
- Upgrade to wolfSSL 5.7.0 or later.
- Rebuild and redeploy applications that link wolfSSL statically.
- Avoid running untrusted code on hosts that handle your RSA private keys.
- Check hardware guidance about memory protections if you operate shared infrastructure.
Why it matters
The record lists CWE-252, unchecked return value, CWE-1256, improper restriction of software interfaces to hardware features, and CWE-74, injection. Rowhammer flips bits in memory by hammering neighbouring rows, and if the flipped bits land in a private key structure, the output of a decryption can leak key material.
Hardware attacks like this are hard to carry out, which is why the score is moderate. The fix makes the code verify its result so a corrupted operation is detected. The record's KEV flag is false.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Does an attacker need local access?
They need to run code on the same machine as the victim process.
Which release fixed it?
wolfSSL 5.7.0 lists the fix in its release notes.
Sources
- wolfSSL 5.7.0 release notes
- Fix pull request 7167 (listed in the NVD record, not retrieved)
- NVD record data for CVE-2024-1545
Last reviewed: 19 October 2026.
