{"answers":{"affected":"1 open source package ship an affected version, including mastodon. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-27399 in the wild and no public exploit code.","fix":"Upgrade mastodon to 4.3.4 or later.","what":"CVE-2025-27399 is a medium-severity missing authorization vulnerability in mastodon, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27399 and fix it if it is affected.\n\nWhat it is: CVE-2025-27399 is a medium-severity missing authorization vulnerability in mastodon, published on 27 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-27399 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mastodon (Bitnami): affected all versions; fixed in 4.3.4\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-2025-27399/ (Markdown: https://insights.sbomify.com/CVE-2025-27399/index.md)","id":"CVE-2025-27399","markdown":"https://insights.sbomify.com/CVE-2025-27399/index.md","name":"CVE-2025-27399","record":{"aliases":["BIT-mastodon-2025-27399","GHSA-94h4-fj37-c825"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Mastodon social platform","requires_auth":"none","summary":"Unapproved users can view private domain block rationales when visibility is restricted to logged-in users, exposing sensitive moderation data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"mastodon","vendor":"joinmastodon"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Mastodon is a self-hosted, federated microblogging platform. In versions prior to 4.1.23, 4.2.16, and 4.3.4, when the visibility for domain blocks/reasons is set to \"users\" (localized English string: \"To logged-in users\"), users that are not yet approved can view the block reasons. Instance admins that do not want their domain blocks to be public are impacted. Versions 4.1.23, 4.2.16, and 4.3.4 fix the 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":"Mastodon's domain blocks \u0026 rationales ignore user approval when visibility set as \"users\"","id":"CVE-2025-27399","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":1,"n_references":4,"next":{"headline":"Magento vulnerable to stored XSS in theme config fields","id":"CVE-2025-27400"},"packages":[{"ecosystem":"Bitnami","fixed":["4.3.4"],"introduced":["0"],"last_affected":[],"package":"mastodon","purl":"pkg:bitnami/mastodon","source":"BIT-mastodon-2025-27399"}],"prev":{"headline":"Command injection in SCALANCE LPE9403","id":"CVE-2025-27398"},"products":["mastodon"],"published":"2025-02-27","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"},{"cvss_score":8.5,"headline":"Lack of media type verification of Activity Streams objects allows impersonation of remote accounts","id":"CVE-2024-25623","kev_date_added":null,"published":"2024-02-19"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-27","vendors":["mastodon"]},"summary":"Unapproved users can view private domain block rationales when visibility is restricted to logged-in users, exposing sensitive moderation data.","url":"https://insights.sbomify.com/CVE-2025-27399/"}