{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23446 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23446 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23446 is a medium-severity denial of service vulnerability in Fortinet FortiEDR, published on 6 Apr 2022. 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-2022-23446 and fix it if it is affected.\n\nWhat it is: CVE-2022-23446 is a medium-severity denial of service vulnerability in Fortinet FortiEDR, published on 6 Apr 2022. 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-2022-23446 in the wild and no public exploit code.\n\nAffected product: Fortinet FortiEDR. 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-2022-23446/ (Markdown: https://insights.sbomify.com/CVE-2022-23446/index.md)","id":"CVE-2022-23446","markdown":"https://insights.sbomify.com/CVE-2022-23446/index.md","name":"CVE-2022-23446","record":{"aliases":["GHSA-r8jj-pf8x-383m"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Fortinet FortiEDR","requires_auth":"high_privilege","summary":"An attacker can cause the FortiEDR application to become unresponsive by modifying its root directory access permissions.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiedr","vendor":"fortinet"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H/E:P/RL:O/RC:C","version":"3.1"},"cwes":[],"description":"A improper control of a resource through its lifetime in Fortinet FortiEDR version 5.0.3 and earlier allows attacker to make the whole application unresponsive via changing its root directory access permission.","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":"Denial of service in Fortinet FortiEDR","id":"CVE-2022-23446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in FortiExtender","id":"CVE-2022-23447"},"packages":[],"prev":{"headline":"Missing authorization in Fortinet FortiSOAR","id":"CVE-2022-23443"},"products":["Fortinet FortiEDR"],"published":"2022-04-06","related":[{"cvss_score":9.1,"headline":"Hardcoded credentials in Fortinet FortiEDR","id":"CVE-2022-23441","kev_date_added":null,"published":"2022-04-06"},{"cvss_score":7.8,"headline":"Hardcoded credentials in Fortinet FortiEDR","id":"CVE-2022-23440","kev_date_added":null,"published":"2022-04-06"},{"cvss_score":7.7,"headline":"Auth bypass in FortiEDR","id":"CVE-2023-33303","kev_date_added":null,"published":"2023-10-13"},{"cvss_score":5.4,"headline":"Cross-site scripting in Fortinet FortiEDR","id":"CVE-2022-29057","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":4.4,"headline":"Security feature bypass in Fortinet FortiEDR","id":"CVE-2022-39949","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":4,"headline":"Missing authorization in FortiEDR CollectorWindows","id":"CVE-2023-44248","kev_date_added":null,"published":"2023-11-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-22","vendors":["Fortinet"]},"summary":"An attacker can cause the FortiEDR application to become unresponsive by modifying its root directory access permissions.","url":"https://insights.sbomify.com/CVE-2022-23446/"}