{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-51489 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-51489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-51489 is a medium-severity vulnerability in ampache, published on 11 Nov 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-51489 and fix it if it is affected.\n\nWhat it is: CVE-2024-51489 is a medium-severity vulnerability in ampache, published on 11 Nov 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-51489 in the wild and no public exploit code.\n\nAffected product: ampache. 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-51489/ (Markdown: https://insights.sbomify.com/CVE-2024-51489/index.md)","id":"CVE-2024-51489","markdown":"https://insights.sbomify.com/CVE-2024-51489/index.md","name":"CVE-2024-51489","record":{"aliases":["GHSA-4q69-983r-mwwr","UBUNTU-CVE-2024-51489"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Ampache streaming application","requires_auth":"low_privilege","summary":"Attackers can forge CSRF attacks to send messages to any user, including administrators, in the Ampache web application.","user_interaction":"not_required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"ampache","vendor":"ampache"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Ampache is a web based audio/video streaming application and file manager. The current implementation of token parsing does not adequately validate CSRF tokens when users send messages to one another. This vulnerability could be exploited to forge CSRF attacks, allowing an attacker to send messages to any user, including administrators, if they interact with a malicious request. This issue has been addressed in version 7.0.1 and all 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":"Insufficient Message Token Validation in Ampache","id":"CVE-2024-51489","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Stored Cross-Site Scripting in Ampache","id":"CVE-2024-51490"},"packages":[],"prev":{"headline":"Insufficient Validation in Delete Message in Ampache","id":"CVE-2024-51488"},"products":["ampache"],"published":"2024-11-11","related":[{"cvss_score":9.3,"headline":"Cross-site Scripting (XSS) - Reflected in ampache/ampache","id":"CVE-2023-0606","kev_date_added":null,"published":"2023-02-01"},{"cvss_score":9.1,"headline":"Unauthenticated SubSonic backend access in Ampache","id":"CVE-2021-21399","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2019-12385","kev_date_added":null,"published":"2019-08-22"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2017-18375","kev_date_added":null,"published":"2019-05-24"},{"cvss_score":8.2,"headline":"Unauthenticated SQL injection in Ampache","id":"CVE-2020-15153","kev_date_added":null,"published":"2021-04-30"},{"cvss_score":7.5,"headline":"Auth bypass in n/a","id":"CVE-2006-5668","kev_date_added":null,"published":"2006-11-03"},{"cvss_score":7.2,"headline":"SQL Injection in ampache/ampache","id":"CVE-2023-0771","kev_date_added":null,"published":"2023-02-10"}],"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-11-12","vendors":["ampache"]},"summary":"Attackers can forge CSRF attacks to send messages to any user, including administrators, in the Ampache web application.","url":"https://insights.sbomify.com/CVE-2024-51489/"}