{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2023-26237 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-26237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-26237 is a medium-severity vulnerability in n/a, published on 5 Oct 2023. 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-2023-26237 and fix it if it is affected.\n\nWhat it is: CVE-2023-26237 is a medium-severity vulnerability in n/a, published on 5 Oct 2023. 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-2023-26237 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-2023-26237/ (Markdown: https://insights.sbomify.com/CVE-2023-26237/index.md)","id":"CVE-2023-26237","markdown":"https://insights.sbomify.com/CVE-2023-26237/index.md","name":"CVE-2023-26237","record":{"aliases":["GHSA-jrwj-fw3w-p28m"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WatchGuard EPDR","requires_auth":"high_privilege","summary":"Attackers can bypass WatchGuard EPDR defensive capabilities by adding a specific registry key as SYSTEM, undermining endpoint protection.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"edr_firmware","vendor":"watchguard"},{"product":"epdr_firmware","vendor":"watchguard"},{"product":"epp_firmware","vendor":"watchguard"},{"product":"panda_ad360_firmware","vendor":"watchguard"}],"cvss":{"score":6.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"An issue was discovered in WatchGuard EPDR 8.0.21.0002. It is possible to bypass the defensive capabilities by adding a registry key as SYSTEM.","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":"Security feature bypass in n/a","id":"CVE-2023-26237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2023-26238"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2023-26236"},"products":["n/a"],"published":"2023-10-05","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2023-26236","kev_date_added":null,"published":"2023-10-05"},{"cvss_score":5.5,"headline":"Missing authorization in n/a","id":"CVE-2023-26238","kev_date_added":null,"published":"2023-10-05"},{"cvss_score":5.5,"headline":"Auth bypass in n/a","id":"CVE-2023-26239","kev_date_added":null,"published":"2023-10-05"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["n/a"]},"summary":"Attackers can bypass WatchGuard EPDR defensive capabilities by adding a specific registry key as SYSTEM, undermining endpoint protection.","url":"https://insights.sbomify.com/CVE-2023-26237/"}