{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-36160 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36160 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36160 is a critical path traversal vulnerability in n/a, published on 6 Jan 2021. 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-2020-36160 and fix it if it is affected.\n\nWhat it is: CVE-2020-36160 is a critical path traversal vulnerability in n/a, published on 6 Jan 2021. 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-2020-36160 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-2020-36160/ (Markdown: https://insights.sbomify.com/CVE-2020-36160/index.md)","id":"CVE-2020-36160","markdown":"https://insights.sbomify.com/CVE-2020-36160/index.md","name":"CVE-2020-36160","record":{"aliases":["GHSA-5g5r-7m54-r43v"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Veritas System Recovery","requires_auth":"none","summary":"A low-privileged user can create a malicious OpenSSL configuration file to achieve arbitrary code execution as SYSTEM upon service startup.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"system_recovery","vendor":"veritas"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:C/UI:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in Veritas System Recovery before 21.2. On start-up, it loads the OpenSSL library from \\usr\\local\\ssl. This library attempts to load the from \\usr\\local\\ssl\\openssl.cnf configuration file, which does not exist. By default, on Windows systems, users can create directories under C:\\. A low privileged user can create a C:\\usr\\local\\ssl\\openssl.cnf configuration file to load a malicious OpenSSL engine, resulting in arbitrary code execution as SYSTEM when the service starts. This gives the attacker administrator access on the system, allowing the attacker (by default) to access all data and installed applications, etc. If the system is also an Active Directory domain controller, then this can affect the entire domain.","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-2020-36160","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-36161"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-36159"},"products":["n/a"],"published":"2021-01-06","related":[{"cvss_score":7.8,"headline":"Other in n/a","id":"CVE-2017-7444","kev_date_added":null,"published":"2017-04-05"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2022-41320","kev_date_added":null,"published":"2022-09-23"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2022-26778","kev_date_added":null,"published":"2022-03-09"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"A low-privileged user can create a malicious OpenSSL configuration file to achieve arbitrary code execution as SYSTEM upon service startup.","url":"https://insights.sbomify.com/CVE-2020-36160/"}