CVE-2024-30187VulnerabilityPublished 25 Mar 2024Updated 22 Aug 2024

CVE-2024-30187: anope · n/a

Affects anopeSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.0.15 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

5.3Medium

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

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

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

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

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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Mar 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-26.

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

Upgrade anope/anope to 2.0.15.

Affected software

Product	Affected	Fixed in
GitHubanope/anope`pkg:github/anope/anope`Other threats	Affected <2.0.15	Fixed in 2.0.15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-30187, organizations should upgrade Anope to version 2.0.15 or later once the patch is released, as this version addresses the password reset issue for suspended accounts. If you cannot patch yet, administrators can implement temporary controls such as disabling password reset functionality for suspended accounts manually or via configuration changes if supported. Monitoring logs for unusual password reset attempts, especially on suspended accounts, can help detect exploitation attempts early. Network-level controls, such as restricting access to IRC service ports to trusted IPs, can reduce exposure. Additionally, enforcing multi-factor authentication (MFA) for account management where possible can add a layer of defense. Educating users and administrators about the risk of account compromise and encouraging strong, unique passwords can also help limit impact. Finally, reviewing and tightening account suspension policies and procedures to ensure suspended accounts are properly flagged and monitored will reduce the risk of unauthorized access.

Description

Anope before 2.0.15 does not prevent resetting the password of a suspended account.

Impact

The primary impact of CVE-2024-30187 is the compromise of confidentiality for suspended user accounts on IRC networks using vulnerable versions of Anope. Attackers can reset passwords without authentication, potentially gaining unauthorized access to these accounts. This could lead to impersonation, unauthorized channel management, or social engineering attacks leveraging the compromised identities. However, the vulnerability does not affect the integrity or availability of the IRC services or the network itself. Since suspended accounts are typically disabled due to policy violations or security concerns, unauthorized access to them could undermine administrative controls and trust in the IRC network. The scope is limited to organizations and communities relying on Anope for IRC services, which may include open-source projects, gaming communities, and private IRC networks. The absence of known exploits and the medium CVSS score suggest a moderate risk, but the ease of exploitation (no privileges or user interaction required) means attackers with network access could leverage this vulnerability. Organizations worldwide that operate IRC networks with Anope should consider the risk of account compromise and potential downstream impacts on their communities.

CWE-281Improper Preservation of Permissions (opens in a new tab)
Base weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 12:03 UTC

WeaknessesCWE-281

Technical details

References

Community reviews

Related threats