{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23441 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23441 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23441 is a critical vulnerability in Fortinet FortiEDR, published on 6 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23441 and fix it if it is affected.\n\nWhat it is: CVE-2022-23441 is a critical vulnerability in Fortinet FortiEDR, published on 6 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23441 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-23441/ (Markdown: https://insights.sbomify.com/CVE-2022-23441/index.md)","id":"CVE-2022-23441","markdown":"https://insights.sbomify.com/CVE-2022-23441/index.md","name":"CVE-2022-23441","record":{"aliases":["GHSA-39xf-jpcr-gmh4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiEDR","requires_auth":"none","summary":"An unauthenticated attacker can use a hard-coded cryptographic key to forge messages and disguise themselves as other collectors in FortiEDR.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortiedr","vendor":"fortinet"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N/E:P/RL:U/RC:C","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"A use of hard-coded cryptographic key vulnerability [CWE-321] in FortiEDR versions 5.0.2, 5.0.1, 5.0.0, 4.0.0 may allow an unauthenticated attacker on the network to disguise as and forge messages from other collectors.","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":"Hardcoded credentials in Fortinet FortiEDR","id":"CVE-2022-23441","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Fortinet FortiOS","id":"CVE-2022-23442"},"packages":[],"prev":{"headline":"Hardcoded credentials in Fortinet FortiEDR","id":"CVE-2022-23440"},"products":["Fortinet FortiEDR"],"published":"2022-04-06","related":[{"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.4,"headline":"Denial of service in Fortinet FortiEDR","id":"CVE-2022-23446","kev_date_added":null,"published":"2022-04-06"},{"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["Fortinet"]},"summary":"An unauthenticated attacker can use a hard-coded cryptographic key to forge messages and disguise themselves as other collectors in FortiEDR.","url":"https://insights.sbomify.com/CVE-2022-23441/"}