dbcve.org
MisskeyApplication

CVE-2024-52592

MEDIUM · 5.3 CVSS v3.1 Published 2024-12-18
Fix available
A fix is available. Upgrade to 2024.11.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Misskey is an open source, federated social media platform. In affected versions missing validation in `ApInboxService.update` allows an attacker to modify the result of polls belonging to another user. No authentication is required, except for a valid signature from any actor on any remote instance. Vulnerable Misskey instances will accept spoofed updates for remote polls. Local polls are unaffected. This issue has been addressed in version 2024.11.0-alpha.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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 · high confidence

Missing validation in the ApInboxService.update function allows remote actors to modify poll results belonging to other users. The vulnerability requires only a valid ActivityPub signature from any actor on any remote federated instance, making exploitation relatively straightforward for adversaries targeting vulnerable Misskey servers.

MitigationUpgrade Misskey instances to version 2024.11.0-alpha.3 or later. No workarounds exist; immediate patching is the only mitigation.

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
MisskeyApplication
Affected:>= 10.92.1, < 2024.11.0= 2024.11.0

CVSS 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
None
Integrity
Low
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Misskey installation
    Locate the Misskey installation directory or check running processes for misskey. Common paths include /opt/misskey, /home/misskey, or check via process manager (systemctl status misskey, pm2 list).
    Affected if Misskey is not installed or not running.
  2. Determine installed Misskey version
    Run 'misskey --version' from the Misskey installation directory, or check package.json version field, or inspect the 'built' metadata file if available in the Misskey root directory.
    Affected if Cannot determine version or Misskey is not present.
  3. Compare version against affected range
    Compare the installed version number to the affected range: >= 10.92.1, < 2024.11.0 OR exactly 2024.11.0. Note that versions 2024.11.0-alpha.1 and 2024.11.0-alpha.2 are also affected.
    Affected if Installed version falls within >= 10.92.1 and < 2024.11.0, or equals 2024.11.0.
  4. Verify ActivityPub federation is enabled
    Check Misskey config files (default: config/default.yml or config/production.yml) for the 'federation' section. Confirm that 'enabled' is set to true, or check if the instance has any followers from remote domains.
    Affected if Federation is enabled and the instance has federated connections - this is required for the attack to be exploitable.

An instance is affected if it runs Misskey version 10.92.1 or higher but lower than 2024.11.0, or exactly 2024.11.0, AND has ActivityPub federation enabled with remote federated connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2024.11.0 or later
Fixed in 2024.11.0
Interim mitigation

Upgrade Misskey instances to version 2024.11.0-alpha.3 or later. No workarounds exist; immediate patching is the only mitigation.

Recommended fix Moderate confidence

2024.11.0-alpha.3 or later stable release

  1. 1. Back up your Misskey instance database and configuration files before upgrading
  2. 2. Stop the Misskey service
  3. 3. Update Misskey to version 2024.11.0-alpha.3 or later stable release that includes the fix
  4. 4. Verify the update was successful
  5. 5. Restart the Misskey service
  6. 6. Test that remote poll updates from federated instances are now properly validated
Caveat Alpha version may not be suitable for production environments; review release notes for any stability or compatibility concerns

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Misskey Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-52592 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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