{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-20735 exists.","fix":"No fix has been published for CVE-2018-20735 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20735 is a high-severity vulnerability in n/a, published on 17 Jan 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-2018-20735 and fix it if it is affected.\n\nWhat it is: CVE-2018-20735 is a high-severity vulnerability in n/a, published on 17 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-20735 exists.\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-20735/ (Markdown: https://insights.sbomify.com/CVE-2018-20735/index.md)","id":"CVE-2018-20735","markdown":"https://insights.sbomify.com/CVE-2018-20735/index.md","name":"CVE-2018-20735","record":{"aliases":["GHSA-pjqr-f9gr-wm84"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"BMC PATROL Agent","requires_auth":"low_privilege","summary":"Low-privileged domain users can escalate to SYSTEM on PATROL Agent hosts due to missing permission checks, enabling lateral movement in Active Directory.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"patrol_agent","vendor":"bmc"}],"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-287","name":"Improper Authentication"}],"description":"An issue was discovered in BMC PATROL Agent through 11.3.01. It was found that the PatrolCli application can allow for lateral movement and escalation of privilege inside a Windows Active Directory environment. It was found that by default the PatrolCli / PATROL Agent application only verifies if the password provided for the given username is correct; it does not verify the permissions of the user on the network. This means if you have PATROL Agent installed on a high value target (domain controller), you can use a low privileged domain user to authenticate with PatrolCli and then connect to the domain controller and run commands as SYSTEM. This means any user on a domain can escalate to domain admin through PATROL Agent. NOTE: the vendor disputes this because they believe it is adequate to prevent this escalation by means of a custom, non-default configuration","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-01-17","github_poc":0,"max_poc_stars":null,"metasploit":1,"nuclei":0,"refs":[{"date":"2019-01-17","kind":"metasploit","ref":"exploit/multi/misc/bmc_patrol_cmd_exec","stars":null,"title":"BMC Patrol Agent Privilege Escalation Cmd Execution"},{"date":"2019-03-18","kind":"exploitdb","ref":"46556","stars":null,"title":"BMC Patrol Agent - Privilege Escalation Code Execution Execution (Metasploit)"}],"tier":"weaponised"},"has_fix":null,"headline":"Privilege escalation in n/a","id":"CVE-2018-20735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-20736"},"packages":[],"prev":{"headline":"XML external entity in n/a","id":"CVE-2018-20733"},"products":["n/a"],"published":"2019-01-17","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2008-5982","kev_date_added":null,"published":"2009-01-27"},{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-1999-0801","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":10,"headline":"Auth bypass in n/a","id":"CVE-1999-0443","kev_date_added":null,"published":"2000-02-04"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-34257","kev_date_added":null,"published":"2023-05-31"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-8352","kev_date_added":null,"published":"2019-05-20"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2020-35593","kev_date_added":null,"published":"2023-09-05"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2019-17043","kev_date_added":null,"published":"2019-10-14"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Low-privileged domain users can escalate to SYSTEM on PATROL Agent hosts due to missing permission checks, enabling lateral movement in Active Directory.","url":"https://insights.sbomify.com/CVE-2018-20735/"}