{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-10204 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-10204 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-10204 is a high-severity vulnerability in n/a, published on 18 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-10204 and fix it if it is affected.\n\nWhat it is: CVE-2018-10204 is a high-severity vulnerability in n/a, published on 18 Apr 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-10204 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-10204/ (Markdown: https://insights.sbomify.com/CVE-2018-10204/index.md)","id":"CVE-2018-10204","markdown":"https://insights.sbomify.com/CVE-2018-10204/index.md","name":"CVE-2018-10204","record":{"aliases":["GHSA-7925-2p2w-mgxj"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"PureVPN Windows client","requires_auth":"low_privilege","summary":"An authenticated attacker can escalate privileges to SYSTEM by modifying an insecure OpenVPN configuration file in PureVPN for Windows.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"purevpn","vendor":"purevpn"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"PureVPN 6.0.1 for Windows suffers from a SYSTEM privilege escalation vulnerability in its \"sevpnclient\" service. When configured to use the OpenVPN protocol, the \"sevpnclient\" service executes \"openvpn.exe\" using the OpenVPN config file located at %PROGRAMDATA%\\purevpn\\config\\config.ovpn. This file allows \"Write\" permissions to users in the \"Everyone\" group. An authenticated attacker may modify this file to specify a dynamic library plugin that should run for every new VPN connection attempt. This plugin will execute code in the context of the SYSTEM account.","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":"Privilege escalation in n/a","id":"CVE-2018-10204","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-10205"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-10201"},"products":["n/a"],"published":"2018-04-18","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-6822","kev_date_added":null,"published":"2018-02-07"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18656","kev_date_added":null,"published":"2018-10-26"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-7484","kev_date_added":null,"published":"2018-02-26"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2023-48957","kev_date_added":null,"published":"2024-08-25"}],"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-09-17","vendors":["n/a"]},"summary":"An authenticated attacker can escalate privileges to SYSTEM by modifying an insecure OpenVPN configuration file in PureVPN for Windows.","url":"https://insights.sbomify.com/CVE-2018-10204/"}