CVE-2024-30172VulnerabilityPublished 9 May 2024Updated 5 Nov 2024

CVE-2024-30172: n/a

Source CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 1.78 : patch affected systems soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.78

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

1. Upgrade to Bouncy Castle Java Cryptography APIs version 1.78 or later as soon as it becomes available to ensure the infinite loop issue is resolved. 2. Implement strict input validation and sanity checks on signatures and public keys before passing them to the verification function to detect malformed or suspicious inputs early. 3. Introduce execution timeouts or watchdog mechanisms around cryptographic verification calls to prevent indefinite blocking or resource exhaustion. 4. Monitor application logs and performance metrics for signs of unusually long verification times or CPU spikes that may indicate exploitation attempts. 5. Restrict exposure of services performing Ed25519 verification to trusted networks or authenticated users where possible to reduce attack surface. 6. Conduct code reviews and fuzz testing on cryptographic components to identify similar logic flaws proactively. 7. Educate development and security teams about the risks of malformed cryptographic inputs and the importance of robust error handling in cryptographic libraries.

Description

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.

Impact

The primary impact of CVE-2024-30172 is a denial-of-service condition caused by an infinite loop during Ed25519 signature verification. Organizations using vulnerable versions of Bouncy Castle in Java applications that perform cryptographic signature verification may experience application hangs, degraded performance, or crashes. This can disrupt critical services such as secure communications, authentication systems, and blockchain or cryptocurrency platforms relying on Ed25519 signatures. The vulnerability does not allow data theft or modification but can be leveraged to cause service outages, potentially impacting business continuity and user trust. Attackers can exploit this remotely without authentication, increasing the risk of widespread disruption. Systems exposed to untrusted inputs or network traffic containing signatures are particularly at risk. The lack of known exploits in the wild currently limits immediate threat but does not diminish the urgency for remediation given the high severity and ease of exploitation.

References

Community reviews

Loading reviews…