Atheme: Improper Authentication
CVE-2022-24976 is a critical-severity improper authentication vulnerability in Atheme, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 7.2.12 as the first without the flaw, so updating Atheme to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.81% chance of exploitation within 30 days, higher than 79% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Atheme to 7.2.12 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.1 | Critical | NVD |
| CVSS 2.0 | 5.8 | Medium | NVD |
Official description
Atheme IRC Services before 7.2.12, when used in conjunction with InspIRCd, allows authentication bypass by ending an IRC handshake at a certain point during a challenge-response login sequence.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/atheme/atheme/commit/4e664c75d0b280a052eb8b5e81aa41944e593c52Third Party Advisory
- github.com/atheme/atheme/compare/v7.2.11...v7.2.12Third Party Advisory
Technical write-ups (may include proof of concept)
- openwall.com/lists/oss-security/2022/01/30/4Exploit, Mailing List, Third Party Advisory
Recent Improper Authentication vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
Spotted an error? Tell us.