{"answers":{"affected":"1 open source package ship an affected version, including mastodon. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-25623 in the wild and no public exploit code.","fix":"Upgrade mastodon to a fixed version for your release line: 3.5.19, 4.0.15, 4.1.15 or 4.2.7.","what":"CVE-2024-25623 is a high-severity vulnerability in mastodon, published on 19 Feb 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-25623 and fix it if it is affected.\n\nWhat it is: CVE-2024-25623 is a high-severity vulnerability in mastodon, published on 19 Feb 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-25623 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mastodon (Bitnami): affected all versions; fixed in 3.5.19, 4.0.15, 4.1.15, 4.2.7\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-25623/ (Markdown: https://insights.sbomify.com/CVE-2024-25623/index.md)","id":"CVE-2024-25623","markdown":"https://insights.sbomify.com/CVE-2024-25623/index.md","name":"CVE-2024-25623","record":{"aliases":["BIT-mastodon-2024-25623","GHSA-jhrq-qvrm-qr36"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Mastodon social network","requires_auth":"low_privilege","summary":"Attackers can impersonate remote accounts by exploiting missing media type verification in Mastodon's Activity Streams fetching logic.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mastodon","vendor":"joinmastodon"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"}],"description":"Mastodon is a free, open-source social network server based on ActivityPub. Prior to versions 4.2.7, 4.1.15, 4.0.15, and 3.5.19, when fetching remote statuses, Mastodon doesn't check that the response from the remote server has a `Content-Type` header value of the Activity Streams media type, which allows a threat actor to upload a crafted Activity Streams document to a remote server and make a Mastodon server fetch it, if the remote server accepts arbitrary user uploads. The vulnerability allows a threat actor to impersonate an account on a remote server that satisfies all of the following properties: allows the attacker to register an account; accepts arbitrary user-uploaded documents and places them on the same domain as the ActivityPub actors; and serves user-uploaded document in response to requests with an `Accept` header value of the Activity Streams media type. Versions 4.2.7, 4.1.15, 4.0.15, and 3.5.19 contain a fix for this issue.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Lack of media type verification of Activity Streams objects allows impersonation of remote accounts","id":"CVE-2024-25623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"other","year":"2024"},"n_packages":1,"n_references":2,"next":{"headline":"iris-web vulnerable to Server Side Template Injection in reports","id":"CVE-2024-25624"},"packages":[{"ecosystem":"Bitnami","fixed":["3.5.19","4.0.15","4.1.15","4.2.7"],"introduced":["0","4.0.0","4.1.0","4.2.0"],"last_affected":[],"package":"mastodon","purl":"pkg:bitnami/mastodon","source":"BIT-mastodon-2024-25623"}],"prev":{"headline":"H2O ignores headers configuration directives","id":"CVE-2024-25622"},"products":["mastodon"],"published":"2024-02-19","related":[{"cvss_score":10,"headline":"Mastodon vulnerable to arbitrary file creation through media attachments","id":"CVE-2023-36460","kev_date_added":null,"published":"2023-07-06"},{"cvss_score":9.8,"headline":"Improper Restriction of Excessive Authentication Attempts in mastodon/mastodon","id":"CVE-2022-2166","kev_date_added":null,"published":"2022-11-16"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2022-24307","kev_date_added":null,"published":"2022-02-03"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-21018","kev_date_added":null,"published":"2019-09-22"},{"cvss_score":9.4,"headline":"Mastodon Remote user impersonation and takeover","id":"CVE-2024-23832","kev_date_added":null,"published":"2024-02-01"},{"cvss_score":9.3,"headline":"Mastodon vulnerable to Cross-site Scripting through oEmbed preview cards","id":"CVE-2023-36459","kev_date_added":null,"published":"2023-07-06"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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-08-01","vendors":["mastodon"]},"summary":"Attackers can impersonate remote accounts by exploiting missing media type verification in Mastodon's Activity Streams fetching logic.","url":"https://insights.sbomify.com/CVE-2024-25623/"}