CVE-2024-49363: Uncontrolled Recursion and Asymmetric Resource Consumption (Amplification) in media/file proxy in Misskey

Published Dec 18, 2024
·
Updated

Misskey is an open source, federated social media platform. In affected versions FileServerService (media proxy) in github.com/misskey-dev/misskey 2024.10.1 or earlier did not detect proxy loops, which allows remote actors to execute a self-propagating reflected/amplified distributed denial-of-service via a maliciously crafted note. FileServerService.prototype.proxyHandler did not check incoming requests are not coming from another proxy server. An attacker can execute an amplified denial-of-service by sending a nested proxy request to the server and end the request with a malicious redirect back to another nested proxy request. Leading to unbounded recursion until the original request is timed out. This issue has been addressed in version 2024.11.0-alpha.3. Users are advised to upgrade. Users unable to upgrade may configure the reverse proxy to block requests to the proxy with an empty User-Agent header or one containing Misskey/. An attacker can not effectively modify the User-Agent header without making another request to the server.

Affected Software

1 affected component
Misskey Misskey<=2024.10.1

Event History

Dec 18, 2024
CVE Published
via MITRE·07:24 PM
Data Sourced
via MITRE·07:24 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:15 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What versions of Misskey are affected by CVE-2024-49363?

CVE-2024-49363 affects Misskey versions up to and including 2024.10.1.

2

What is the main threat posed by CVE-2024-49363?

CVE-2024-49363 allows remote actors to execute self-propagating reflected or amplified distributed attacks due to the lack of proxy loop detection in FileServerService.

3

How can I fix CVE-2024-49363 in my Misskey installation?

To mitigate CVE-2024-49363, upgrade your Misskey installation to a version later than 2024.10.1.

4

Is there a workaround for CVE-2024-49363 until I can upgrade?

There are no official workarounds for CVE-2024-49363; upgrading is the recommended action.

5

What should I do if I am compromised due to CVE-2024-49363?

If compromised due to CVE-2024-49363, immediate investigation and remediation steps should be taken to secure your system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203