{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-15832 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15832 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15832 is a high-severity command injection vulnerability in n/a, published on 20 Sep 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-15832 and fix it if it is affected.\n\nWhat it is: CVE-2018-15832 is a high-severity command injection vulnerability in n/a, published on 20 Sep 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-15832 in the wild and no public exploit code.\n\nAffected product: n/a. 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-15832/ (Markdown: https://insights.sbomify.com/CVE-2018-15832/index.md)","id":"CVE-2018-15832","markdown":"https://insights.sbomify.com/CVE-2018-15832/index.md","name":"CVE-2018-15832","record":{"aliases":["GHSA-6pxp-rm7g-gpvq"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Uplay Desktop Client","requires_auth":"none","summary":"Remote attackers can execute arbitrary code via malicious URI handlers in the Uplay Desktop Client, requiring user interaction.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"uplay","vendor":"ubisoft"}],"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-20","name":"Improper Input Validation"}],"description":"upc.exe in Ubisoft Uplay Desktop Client versions 63.0.5699.0 allows remote attackers to execute arbitrary code. 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-09-30","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-09-30T20:40:31Z","kind":"github_poc","ref":"https://github.com/anon135792408/Ubisoft-Uplay-Desktop-Client-63.0.5699.0","stars":0,"title":"CVE-2018-15832"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2018-15832","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":"Business logic in n/a","id":"CVE-2018-15833"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-15822"},"products":["n/a"],"published":"2018-09-20","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-14737","kev_date_added":null,"published":"2019-10-14"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code via malicious URI handlers in the Uplay Desktop Client, requiring user interaction.","url":"https://insights.sbomify.com/CVE-2018-15832/"}