{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-1167 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-1167 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-1167 is a high-severity command injection vulnerability in Spotify Music Player, published on 19 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-1167 and fix it if it is affected.\n\nWhat it is: CVE-2018-1167 is a high-severity command injection vulnerability in Spotify Music Player, published on 19 Apr 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-1167 in the wild and no public exploit code.\n\nAffected product: Spotify Music Player. 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-2018-1167/ (Markdown: https://insights.sbomify.com/CVE-2018-1167/index.md)","id":"CVE-2018-1167","markdown":"https://insights.sbomify.com/CVE-2018-1167/index.md","name":"CVE-2018-1167","record":{"aliases":["GHSA-9rj9-5mm5-q8fc"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Spotify Music Player","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via malicious URI handlers in Spotify Music Player, requiring user interaction to trigger the flaw.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"zdi","cpe":[{"product":"spotify","vendor":"spotify"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Spotify Music Player 1.0.69.336. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of URI handlers. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code under the context of the current process. Was ZDI-CAN-5501.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in Spotify Music Player","id":"CVE-2018-1167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in ABB MicroSCADA","id":"CVE-2018-1168"},"packages":[],"prev":{"headline":"Use after free in Joyent SmartOS","id":"CVE-2018-1166"},"products":["Spotify Music Player"],"published":"2018-04-19","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["Spotify"]},"summary":"Remote attackers can execute arbitrary code via malicious URI handlers in Spotify Music Player, requiring user interaction to trigger the flaw.","url":"https://insights.sbomify.com/CVE-2018-1167/"}