CVE-2022-24976 json
Atheme IRC Services before 7.2.12, when used in conjunction with InspIRCd, allows authentication bypass by ending an IRC handshake at a cer…
published 4y ago modified 4mo ago also EUVD-2022-29726
- cvss
- 9.1
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- atheme atheme 7.2.12
- atheme-services Debian 14, Debian 13, Debian 12 7.2.12-1
debian advisories DEBIAN-CVE-2022-24976
- atheme openSUSE Tumbleweed 7.2.12-2.1
- atheme Package Hub 15 SP4, openSUSE Leap 15.4 7.2.12-bp154.2.3.1
- atheme Package Hub 15 SP3, openSUSE Leap 15.3 7.2.12-bp153.2.3.1
opensuse advisories openSUSE-SU-2024:11848-1openSUSE-SU-2022:10019-1openSUSE-SU-2022:10018-1
Is CVE-2022-24976 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.81% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- openwall.com https://www.openwall.com/lists/oss-security/2022/01/30/4 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-287 Improper Authentication
References
-
github.com
/atheme/atheme/commit/4e664c75d0b280a052eb8b5e81aa41944e593c52
patch, third-party-advisory
-
github.com
/atheme/atheme/compare/v7.2.11...v7.2.12
patch, third-party-advisory
-
openwall.com
/lists/oss-security/2022/01/30/4
exploit, mailing-list, third-party-advisory
Sources
- CVE List CVE-2022-24976
- NVD CVE-2022-24976
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.