CVE-2022-24307
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMastodon before 3.3.2 and 3.4.x before 3.4.6 has incorrect access control because it does not compact incoming signed JSON-LD activities. (JSON-LD signing has been supported since version 1.6.0.)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMastodon versions before 3.3.2 and 3.4.6 contain an incorrect access control vulnerability due to failure to compact incoming signed JSON-LD activities. This allows attackers to bypass authentication and authorization checks in the ActivityPub federation protocol by sending specially crafted JSON-LD that bypasses signature verification.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.3.2>= 3.4.0, < 3.4.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Mastodon versionCheck the version file in the Mastodon installation directory, the Gemfile.lock, or the admin dashboard under Site Settings. Common locations include the VERSION file in the root directory or running 'git describe --tags' if installed from source.Affected if Version is below 3.3.2 or between 3.4.0 and 3.4.5 (inclusive)
-
Verify ActivityPub federation is enabledCheck Mastodon's site settings or configuration file (config/settings.yml) for the 'activitypub' or 'federation' enabled status. In the admin interface, confirm that federated timeline (FEP) is not disabled.Affected if ActivityPub federation is currently active (this is the default and typical configuration)
-
Inspect inbound JSON-LD processingReview web server and application logs for any unusual or malformed JSON-LD activity submissions, particularly those involving the /inbox endpoints. Check if there are any existing signatures that appear to bypass standard verification.Affected if Unusual inbound ActivityPub requests are observed or if signature validation has been bypassed historically
-
Check for unauthorized access indicatorsReview account moderation logs, audit logs, and remote follow requests for signs of unauthorized account access or actions performed by federated accounts that should have been rejected.Affected if Any unauthorized federated account actions are found that bypassed normal authentication
You are affected if running Mastodon version 3.3.0-3.3.1 or 3.4.0-3.4.5 with ActivityPub federation enabled, as the JSON-LD compaction flaw allows signature verification bypass on inbound federation requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.3.23.4.6
Upgrade Mastodon to version 3.3.2 or 3.4.6 or later to patch the vulnerability. This is a critical security update that should be prioritized given the CVSS 9.8 score.
Mastodon 3.3.2 or 3.4.6 (or latest stable release in your minor branch)
- Ensure you have a backup of your Mastodon instance before upgrading
- Determine your current Mastodon version by checking your installation
- If running < 3.3.2, upgrade to version 3.3.2 or later
- If running >= 3.4.0 and < 3.4.6, upgrade to version 3.4.6 or later
- Follow standard Mastodon upgrade procedures for your deployment method (e.g., source, Docker, or package manager)
- After upgrading, verify the instance is functioning correctly and monitor for any issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24307 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24307 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data