{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12572 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12572 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12572 is a high-severity path traversal vulnerability in n/a, published on 21 Jun 2019. 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-2019-12572 and fix it if it is affected.\n\nWhat it is: CVE-2019-12572 is a high-severity path traversal vulnerability in n/a, published on 21 Jun 2019. 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-2019-12572 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-2019-12572/ (Markdown: https://insights.sbomify.com/CVE-2019-12572/index.md)","id":"CVE-2019-12572","markdown":"https://insights.sbomify.com/CVE-2019-12572/index.md","name":"CVE-2019-12572","record":{"aliases":["GHSA-h2fp-jc27-vpq5"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PIA VPN Client","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges to SYSTEM by placing a malicious OpenSSL config file in a predictable path loaded by the PIA VPN service.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"private_internet_access","vendor":"londontrustmedia"}],"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-427","name":"Uncontrolled Search Path Element"}],"description":"A vulnerability in the London Trust Media Private Internet Access (PIA) VPN Client 1.0.2 (build 02363) for Windows could allow an authenticated, local attacker to run arbitrary code with elevated privileges. On startup, the PIA Windows service (pia-service.exe) loads the OpenSSL library from %PROGRAMFILES%\\Private Internet Access\\libeay32.dll. This library attempts to load the C:\\etc\\ssl\\openssl.cnf configuration file which does not exist. By default on Windows systems, authenticated users can create directories under C:\\. A low privileged user can create a C:\\etc\\ssl\\openssl.cnf configuration file to load a malicious OpenSSL engine library resulting in arbitrary code execution as SYSTEM when the service starts.","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":"Path traversal in n/a","id":"CVE-2019-12572","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2019-12573"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2019-12571"},"products":["n/a"],"published":"2019-06-21","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-10190","kev_date_added":null,"published":"2018-04-17"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2017-15882","kev_date_added":null,"published":"2017-10-26"}],"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-08-04","vendors":["n/a"]},"summary":"Local attackers can escalate privileges to SYSTEM by placing a malicious OpenSSL config file in a predictable path loaded by the PIA VPN service.","url":"https://insights.sbomify.com/CVE-2019-12572/"}