{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2020-36166 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-36166 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-36166 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-36166 and fix it if it is affected.\n\nWhat it is: CVE-2020-36166 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-36166 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-36166/ (Markdown: https://insights.sbomify.com/CVE-2020-36166/index.md)","id":"CVE-2020-36166","markdown":"https://insights.sbomify.com/CVE-2020-36166/index.md","name":"CVE-2020-36166","record":{"aliases":["GHSA-37w4-w4g6-8f3q"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Veritas InfoScale","requires_auth":"none","summary":"A low-privileged user can exploit an insecure library path to load a malicious OpenSSL engine, achieving arbitrary code execution as SYSTEM.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"infoscale","vendor":"veritas"},{"product":"infoscale_operations_manager","vendor":"veritas"},{"product":"storage_foundation","vendor":"veritas"},{"product":"storage_foundation_and_high_availability","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 InfoScale 7.x through 7.4.2 on Windows, Storage Foundation through 6.1 on Windows, Storage Foundation HA through 6.1 on Windows, and InfoScale Operations Manager (aka VIOM) Windows Management Server 7.x through 7.4.2. On start-up, it loads the OpenSSL library from \\usr\\local\\ssl. This library attempts to load the \\usr\\local\\ssl\\openssl.cnf configuration file, which may not exist. On Windows systems, this path could translate to \u003cdrive\u003e:\\usr\\local\\ssl\\openssl.cnf, where \u003cdrive\u003e could be the default Windows installation drive such as C:\\ or the drive where a Veritas product is installed. By default, on Windows systems, users can create directories under any top-level directory. A low privileged user can create a \u003cdrive\u003e:\\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, access all installed applications, etc.","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-36166","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":"Path traversal in n/a","id":"CVE-2020-36167"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2020-36165"},"products":["n/a"],"published":"2021-01-06","related":[],"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 exploit an insecure library path to load a malicious OpenSSL engine, achieving arbitrary code execution as SYSTEM.","url":"https://insights.sbomify.com/CVE-2020-36166/"}