{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-52579 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-52579 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-52579 is a medium-severity server-side request forgery vulnerability in misskey-dev misskey, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52579 and fix it if it is affected.\n\nWhat it is: CVE-2024-52579 is a medium-severity server-side request forgery vulnerability in misskey-dev misskey, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-52579 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-52579/ (Markdown: https://insights.sbomify.com/CVE-2024-52579/index.md)","id":"CVE-2024-52579","markdown":"https://insights.sbomify.com/CVE-2024-52579/index.md","name":"CVE-2024-52579","record":{"aliases":["GHSA-5q3h-wpfw-hjjw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Misskey social platform","requires_auth":"low_privilege","summary":"Attackers can exploit improper host checks in Misskey APIs to send requests to internal servers, potentially accessing private network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"misskey","vendor":"misskey"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Misskey is an open source, federated social media platform. Some APIs using `HttpRequestService` do not properly check the target host. This vulnerability allows an attacker to send POST or GET requests to the internal server, which may result in a SSRF attack.It allows an attacker to send POST or GET requests (with some controllable URL parameters) to private IPs, enabling further attacks on internal servers. 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.","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":"Server-Side Request Forgery vulnerability in various APIs in Misskey","id":"CVE-2024-52579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Litestar allows unbounded resource consumption (DoS vulnerability)","id":"CVE-2024-52581"},"packages":[],"prev":{"headline":"Apache Ignite: Possible RCE when deserializing incoming messages by the server node","id":"CVE-2024-52577"},"products":["misskey"],"published":"2024-12-18","related":[{"cvss_score":9.3,"headline":"Misskey's Incomplete Patch of CVE-2024-52591 Leads to Forgery of Federated Notes","id":"CVE-2025-25306","kev_date_added":null,"published":"2025-03-10"},{"cvss_score":9.3,"headline":"Misskey's missing signature validation allows arbitrary users to impersonate any remote user.","id":"CVE-2023-49079","kev_date_added":null,"published":"2023-11-29"},{"cvss_score":9.2,"headline":"Misskey lacks proper authorization checks and input validation","id":"CVE-2026-28431","kev_date_added":null,"published":"2026-03-09"},{"cvss_score":9.1,"headline":"Misskey vulnerable to improper authorization when accessing with third-party application","id":"CVE-2023-52139","kev_date_added":null,"published":"2023-12-29"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles in Misskey","id":"CVE-2024-52590","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"Missing validation allows spoofed profiles and notes in Misskey","id":"CVE-2024-52591","kev_date_added":null,"published":"2024-12-18"},{"cvss_score":8.8,"headline":"SQL injection of notes/search-by-tag","id":"CVE-2023-24812","kev_date_added":null,"published":"2023-02-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"Attackers can exploit improper host checks in Misskey APIs to send requests to internal servers, potentially accessing private network resources.","url":"https://insights.sbomify.com/CVE-2024-52579/"}