{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11081 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11081 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11081 is a medium-severity vulnerability in osquery, published on 10 Jul 2020. 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-2020-11081 and fix it if it is affected.\n\nWhat it is: CVE-2020-11081 is a medium-severity vulnerability in osquery, published on 10 Jul 2020. 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-2020-11081 in the wild and no public exploit code.\n\nAffected product: osquery. 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-11081/ (Markdown: https://insights.sbomify.com/CVE-2020-11081/index.md)","id":"CVE-2020-11081","markdown":"https://insights.sbomify.com/CVE-2020-11081/index.md","name":"CVE-2020-11081","record":{"aliases":["GHSA-2xwp-8fv7-c5pm"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"osquery endpoint agent","requires_auth":"low_privilege","summary":"Local attackers can escalate privileges by placing a malicious DLL in a user-writable PATH directory, exploiting osquery's DLL search order.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"osquery","vendor":"linuxfoundation"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-426","name":"Untrusted Search Path"},{"id":"CWE-114","name":"Process Control"}],"description":"osquery before version 4.4.0 enables a privilege escalation vulnerability. If a Window system is configured with a PATH that contains a user-writable directory then a local user may write a zlib1.dll DLL, which osquery will attempt to load. Since osquery runs with elevated privileges this enables local escalation. This is fixed in version 4.4.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"osquery susceptible to DLL search order hijacking of zlib1.dll","id":"CVE-2020-11081","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2020"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-Site Scripting in Kaminari","id":"CVE-2020-11082"},"packages":[],"prev":{"headline":"Denial of service in nghttp2","id":"CVE-2020-11080"},"products":["osquery"],"published":"2020-07-10","related":[{"cvss_score":9.1,"headline":"Weak cryptography in Osquery","id":"CVE-2020-1887","kev_date_added":null,"published":"2020-03-12"},{"cvss_score":8.1,"headline":"Path traversal in osquery","id":"CVE-2019-3567","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":7.8,"headline":"Security feature bypass in osquery","id":"CVE-2018-6336","kev_date_added":null,"published":"2018-12-31"},{"cvss_score":5.2,"headline":"sqlite ATTACH allows some filesystem access","id":"CVE-2020-26273","kev_date_added":null,"published":"2020-12-16"}],"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":["osquery"]},"summary":"Local attackers can escalate privileges by placing a malicious DLL in a user-writable PATH directory, exploiting osquery's DLL search order.","url":"https://insights.sbomify.com/CVE-2020-11081/"}