{"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-25619 in the wild and no public exploit code.","fix":"Upgrade mastodon to 4.2.6 or later.","what":"CVE-2024-25619 is a low-severity missing authorization vulnerability in mastodon, published on 14 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-25619 and fix it if it is affected.\n\nWhat it is: CVE-2024-25619 is a low-severity missing authorization vulnerability in mastodon, published on 14 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-25619 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mastodon (Bitnami): affected all versions; fixed in 4.2.6\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-25619/ (Markdown: https://insights.sbomify.com/CVE-2024-25619/index.md)","id":"CVE-2024-25619","markdown":"https://insights.sbomify.com/CVE-2024-25619/index.md","name":"CVE-2024-25619","record":{"aliases":["BIT-mastodon-2024-25619","GHSA-7w3c-p9j8-mq3x"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mastodon social network","requires_auth":"low_privilege","summary":"Destroyed OAuth applications could continue streaming user data because the streaming server was not notified of token revocation.","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":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-672","name":"Operation on a Resource after Expiration or Release"},{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Mastodon is a free, open-source social network server based on ActivityPub. When an OAuth Application is destroyed, the streaming server wasn't being informed that the Access Tokens had also been destroyed, this could have posed security risks to users by allowing an application to continue listening to streaming after the application had been destroyed. Essentially this comes down to the fact that when Doorkeeper sets up the relationship between Applications and Access Tokens, it uses a `dependent: delete_all` configuration, which means the `after_commit` callback setup on `AccessTokenExtension` didn't actually fire, since `delete_all` doesn't trigger ActiveRecord callbacks. To mitigate, we need to add a `before_destroy` callback to `ApplicationExtension` which announces to streaming that all the Application's Access Tokens are being \"killed\". Impact should be negligible given the affected application had to be owned by the user. None the less this issue has been addressed in versions 4.2.6, 4.1.14, 4.0.14, and 3.5.18. Users are advised to upgrade. There are no known workaround for this vulnerability.","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":"Destroying OAuth Applications doesn't notify Streaming of Access Tokens being destroyed in mastodon","id":"CVE-2024-25619","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2024"},"n_packages":1,"n_references":2,"next":{"headline":"Dependency management path traversal in helm","id":"CVE-2024-25620"},"packages":[{"ecosystem":"Bitnami","fixed":["4.2.6"],"introduced":["0"],"last_affected":[],"package":"mastodon","purl":"pkg:bitnami/mastodon","source":"BIT-mastodon-2024-25619"}],"prev":{"headline":"External OpenID Connect Account Takeover by E-Mail Change in mastodon","id":"CVE-2024-25618"},"products":["mastodon"],"published":"2024-02-14","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-01","vendors":["mastodon"]},"summary":"Destroyed OAuth applications could continue streaming user data because the streaming server was not notified of token revocation.","url":"https://insights.sbomify.com/CVE-2024-25619/"}