{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7484 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7484 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7484 is a high-severity vulnerability in n/a, published on 26 Feb 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-7484 and fix it if it is affected.\n\nWhat it is: CVE-2018-7484 is a high-severity vulnerability in n/a, published on 26 Feb 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-7484 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-7484/ (Markdown: https://insights.sbomify.com/CVE-2018-7484/index.md)","id":"CVE-2018-7484","markdown":"https://insights.sbomify.com/CVE-2018-7484/index.md","name":"CVE-2018-7484","record":{"aliases":["GHSA-qr57-c849-39j8"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PureVPN Windows client","requires_auth":"none","summary":"Local attackers can escalate privileges to SYSTEM via DLL hijacking due to insecure library loading and permissive directory permissions in the PureVPN Windows client.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"purevpn","vendor":"purevpn"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"An issue was discovered in PureVPN through 5.19.4.0 on Windows. The client installation grants the Everyone group Full Control permission to the installation directory. In addition, the PureVPNService.exe service, which runs under NT Authority\\SYSTEM privileges, tries to load several dynamic-link libraries using relative paths instead of the absolute path. When not using a fully qualified path, the application will first try to load the library from the directory from which the application is started. As the residing directory of PureVPNService.exe is writable to all users, this makes the application susceptible to privilege escalation through DLL hijacking.","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-7484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-7485"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2018-7482"},"products":["n/a"],"published":"2018-02-26","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":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-10204","kev_date_added":null,"published":"2018-04-18"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18656","kev_date_added":null,"published":"2018-10-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-16","vendors":["n/a"]},"summary":"Local attackers can escalate privileges to SYSTEM via DLL hijacking due to insecure library loading and permissive directory permissions in the PureVPN Windows client.","url":"https://insights.sbomify.com/CVE-2018-7484/"}