{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18656 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18656 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18656 is a high-severity vulnerability in n/a, published on 26 Oct 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-18656 and fix it if it is affected.\n\nWhat it is: CVE-2018-18656 is a high-severity vulnerability in n/a, published on 26 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-18656 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-18656/ (Markdown: https://insights.sbomify.com/CVE-2018-18656/index.md)","id":"CVE-2018-18656","markdown":"https://insights.sbomify.com/CVE-2018-18656/index.md","name":"CVE-2018-18656","record":{"aliases":["GHSA-r5f4-vq84-cr57"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PureVPN Windows client","requires_auth":"low_privilege","summary":"The PureVPN Windows client stores login credentials in cleartext, allowing local users to read them and potentially take over accounts.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"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:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"The PureVPN client before 6.1.0 for Windows stores Login Credentials (username and password) in cleartext. The location of such files is %PROGRAMDATA%\\purevpn\\config\\login.conf. Additionally, all local users can read this file.","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":"Hardcoded credentials in n/a","id":"CVE-2018-18656","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-18657"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-18655"},"products":["n/a"],"published":"2018-10-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":"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":"The PureVPN Windows client stores login credentials in cleartext, allowing local users to read them and potentially take over accounts.","url":"https://insights.sbomify.com/CVE-2018-18656/"}