{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-49363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-49363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-49363 is a high-severity denial of service vulnerability in misskey-dev misskey, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-49363 and fix it if it is affected.\n\nWhat it is: CVE-2024-49363 is a high-severity denial of service vulnerability in misskey-dev misskey, published on 18 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-49363 in the wild and no public exploit code.\n\nAffected product: misskey-dev misskey. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-49363/ (Markdown: https://insights.sbomify.com/CVE-2024-49363/index.md)","id":"CVE-2024-49363","markdown":"https://insights.sbomify.com/CVE-2024-49363/index.md","name":"CVE-2024-49363","record":{"aliases":["GHSA-gq5q-c77c-v236"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Misskey social media","requires_auth":"none","summary":"Remote attackers can cause denial of service in Misskey via uncontrolled recursion in the media proxy, requiring an upgrade to fix.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"},{"id":"CWE-405","name":"Asymmetric Resource Consumption (Amplification)"}],"description":"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.\nLeading 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Uncontrolled Recursion and Asymmetric Resource Consumption (Amplification) in media/file proxy in Misskey","id":"CVE-2024-49363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"tiny-secp256k1 vulnerable to private key extraction when signing a malicious JSON-stringifyable message in bundled environment","id":"CVE-2024-49364"},"packages":[],"prev":{"headline":"Remote Code Execution on click of \u003ca\u003e Link in markdown preview","id":"CVE-2024-49362"},"products":["misskey"],"published":"2024-12-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-12-19","vendors":["misskey-dev"]},"summary":"Remote attackers can cause denial of service in Misskey via uncontrolled recursion in the media proxy, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2024-49363/"}