First published: Thu May 09 2024(Updated: )
An issue was discovered in Bouncy Castle Java Cryptography APIs before 1.78. An Ed25519 verification code infinite loop can occur via a crafted signature and public key.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.bouncycastle:bctls-jdk15to18 | >=1.73<1.78 | 1.78 |
maven/org.bouncycastle:bctls-jdk14 | >=1.73<1.78 | 1.78 |
maven/org.bouncycastle:bctls-jdk18on | >=1.73<1.78 | 1.78 |
maven/org.bouncycastle:bcprov-jdk14 | >=1.73<1.78 | 1.78 |
maven/org.bouncycastle:bcprov-jdk15to18 | >=1.73<1.78 | 1.78 |
maven/org.bouncycastle:bcprov-jdk18on | >=1.73<1.78 | 1.78 |
nuget/BouncyCastle.Cryptography | <2.3.1 | 2.3.1 |
nuget/BouncyCastle | <2.3.1 | |
redhat/org.bouncycastle-bcprov-jdk18on | <1.78 | 1.78 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-30172 is considered a high severity vulnerability due to its potential to cause denial of service via an infinite loop.
To fix CVE-2024-30172, upgrade to Bouncy Castle Java Cryptography APIs version 1.78 or later.
CVE-2024-30172 affects multiple Bouncy Castle packages and versions prior to 1.78.
CVE-2024-30172 involves an infinite loop issue in Ed25519 verification due to crafted signatures and public keys.
Yes, the infinite loop vulnerability in CVE-2024-30172 can potentially be exploited remotely by delivering a malicious signature.