CVE-2022-46405 json
Mastodon through 4.0.2 allows attackers to cause a denial of service (large Sidekiq pull queue) by creating bot accounts that follow attack…
published 2022-12-04 3 y ago modified 2026-09-08 2 mo ago also BIT-mastodon-2022-46405 , EUVD-2022-49214
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
Mastodon through 4.0.2 allows attackers to cause a denial of service (large Sidekiq pull queue) by creating bot accounts that follow attacker-controlled accounts on certain other servers associated with a wildcard DNS A record, such that there is uncontrolled recursion of attacker-generated messages.
Patch / fix
- bitnami mastodon 4.0.3
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
0.98% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- hackmd.io https://hackmd.io/rD9nsTz1QeuPT-erxqjY-A referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mastodon | <4.0.3 |
4.0.3 |
Classification
- Weakness
-
- CWE-674 Uncontrolled Recursion
References
-
hackmd.io
/rD9nsTz1QeuPT-erxqjY-A
exploit, issue-tracking, third-party-advisory, advisory
-
borg.social
/notes/98bcoo2t1n
issue-tracking, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-46405
web
Sources
- CVE List CVE-2022-46405
- NVD CVE-2022-46405
- OSV BIT-mastodon-2022-46405
Fencer Vulns 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.