{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28194 exists.","fix":"No fix has been published for CVE-2024-28194 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-28194 is a critical vulnerability in Yooooomi your_spotify, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-28194 and fix it if it is affected.\n\nWhat it is: CVE-2024-28194 is a critical vulnerability in Yooooomi your_spotify, published on 13 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-28194 exists.\n\nAffected product: Yooooomi your_spotify. 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-28194/ (Markdown: https://insights.sbomify.com/CVE-2024-28194/index.md)","id":"CVE-2024-28194","markdown":"https://insights.sbomify.com/CVE-2024-28194/index.md","name":"CVE-2024-28194","record":{"aliases":["GHSA-gvcr-g265-j827"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Spotify tracking dashboard","requires_auth":"none","summary":"Attackers can forge authentication tokens using a hardcoded secret to bypass authentication and access arbitrary user accounts, including admin privileges.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"your_spotify","vendor":"yooooomi"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"your_spotify is an open source, self hosted Spotify tracking dashboard. YourSpotify versions \u003c 1.8.0 use a hardcoded JSON Web Token (JWT) secret to sign authentication tokens. Attackers can use this well-known value to forge valid authentication tokens for arbitrary users. This vulnerability allows attackers to bypass authentication and authenticate as arbitrary YourSpotify users, including admin users. This issue has been addressed in version 1.8.0. 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":"weaponised"},"has_fix":false,"headline":"Authentication Bypass Because of Hardcoded JWT Secret in your_spotify","id":"CVE-2024-28194","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-Site Request Forgery (CSRF) vulnerability in API and login in your_spotify","id":"CVE-2024-28195"},"packages":[],"prev":{"headline":"Disclosure of Spotify API Access Tokens to Guest Users Using Public Tokens in your_spotify","id":"CVE-2024-28193"},"products":["your_spotify"],"published":"2024-03-13","related":[{"cvss_score":8.1,"headline":"Cross-Site Request Forgery (CSRF) vulnerability in API and login in your_spotify","id":"CVE-2024-28195","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":6.5,"headline":"Disclosure of Spotify API Access Tokens to Guest Users Using Public Tokens in your_spotify","id":"CVE-2024-28193","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":6.5,"headline":"Clickjacking in your_spotify","id":"CVE-2024-28196","kev_date_added":null,"published":"2024-03-13"},{"cvss_score":5.3,"headline":"NoSQL Injection Leading to Authentication Bypass in your_spotify","id":"CVE-2024-28192","kev_date_added":null,"published":"2024-03-13"}],"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":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-02","vendors":["Yooooomi"]},"summary":"Attackers can forge authentication tokens using a hardcoded secret to bypass authentication and access arbitrary user accounts, including admin privileges.","url":"https://insights.sbomify.com/CVE-2024-28194/"}