{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-11479 exists.","fix":"No fix has been published for CVE-2018-11479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11479 is a high-severity command injection vulnerability in n/a, published on 25 May 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11479 and fix it if it is affected.\n\nWhat it is: CVE-2018-11479 is a high-severity command injection vulnerability in n/a, published on 25 May 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-11479 exists.\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-11479/ (Markdown: https://insights.sbomify.com/CVE-2018-11479/index.md)","id":"CVE-2018-11479","markdown":"https://insights.sbomify.com/CVE-2018-11479/index.md","name":"CVE-2018-11479","record":{"aliases":["GHSA-mcm6-4273-92rf"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Windscribe VPN client","requires_auth":"low_privilege","summary":"An attacker can execute arbitrary commands with SYSTEM privileges via the WindscribeService named pipe due to lack of input validation.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"windscribe","vendor":"windscribe"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The VPN component in Windscribe 1.81 uses the OpenVPN client for connections. Also, it creates a WindScribeService.exe system process that establishes a \\\\.\\pipe\\WindscribeService named pipe endpoint that allows the Windscribe VPN process to connect and execute an OpenVPN process or other processes (like taskkill, etc.). There is no validation of the program name before constructing the lpCommandLine argument for a CreateProcess call. An attacker can run any malicious process with SYSTEM privileges through this named pipe.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-05-24","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2018-05-24","kind":"metasploit","ref":"exploit/windows/local/windscribe_windscribeservice_priv_esc","stars":null,"title":"Windscribe WindscribeService Named Pipe Privilege Escalation"},{"date":"2020-02-07","kind":"exploitdb","ref":"48021","stars":null,"title":"Windscribe - WindscribeService Named Pipe Privilege Escalation (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2018-11479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2018-11481"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2018-11478"},"products":["n/a"],"published":"2018-05-25","related":[{"cvss_score":7.8,"headline":"Windscribe Directory Traversal Local Privilege Escalation Vulnerability","id":"CVE-2024-6141","kev_date_added":null,"published":"2024-08-21"},{"cvss_score":7.8,"headline":"Privilege escalation in Windscribe","id":"CVE-2022-41141","kev_date_added":null,"published":"2023-01-26"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-22809","kev_date_added":null,"published":"2021-05-10"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-27518","kev_date_added":null,"published":"2021-05-04"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-11334","kev_date_added":null,"published":"2018-05-23"},{"cvss_score":7.3,"headline":"Windscribe for Linux 'changeMTU' local privilege escalation","id":"CVE-2025-65199","kev_date_added":null,"published":"2025-12-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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can execute arbitrary commands with SYSTEM privileges via the WindscribeService named pipe due to lack of input validation.","url":"https://insights.sbomify.com/CVE-2018-11479/"}