{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-22300 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22300 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22300 is a medium-severity vulnerability in Fortinet Fortianalyzer, published on 1 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22300 and fix it if it is affected.\n\nWhat it is: CVE-2022-22300 is a medium-severity vulnerability in Fortinet Fortianalyzer, published on 1 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-22300 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortianalyzer. 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-22300/ (Markdown: https://insights.sbomify.com/CVE-2022-22300/index.md)","id":"CVE-2022-22300","markdown":"https://insights.sbomify.com/CVE-2022-22300/index.md","name":"CVE-2022-22300","record":{"aliases":["GHSA-69m8-6m2p-9wrw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet management server","requires_auth":"low_privilege","summary":"Attackers can bypass device policies to force password changes for users in FortiAnalyzer and FortiManager, requiring administrators to upgrade to patched versions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortianalyzer","vendor":"fortinet"},{"product":"fortimanager","vendor":"fortinet"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/E:P/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-755","name":"Improper Handling of Exceptional Conditions"}],"description":"A improper handling of insufficient permissions or privileges in Fortinet FortiAnalyzer version 5.6.0 through 5.6.11, FortiAnalyzer version 6.0.0 through 6.0.11, FortiAnalyzer version 6.2.0 through 6.2.9, FortiAnalyzer version 6.4.0 through 6.4.7, FortiAnalyzer version 7.0.0 through 7 .0.2, FortiManager version 5.6.0 through 5.6.11, FortiManager version 6.0.0 through 6.0.11, FortiManager version 6.2.0 through 6.2.9, FortiManager version 6.4.0 through 6.4.7, FortiManager version 7.0.0 through 7.0.2 allows attacker to bypass the device policy and force the password-change action for its user.","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 Fortinet FortiManager, FortiAnalyzer","id":"CVE-2022-22300","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortianalyzer","products":["fortinet:fortianalyzer","fortinet:fortimanager"],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in Fortinet FortiAP-C","id":"CVE-2022-22301"},"packages":[],"prev":{"headline":"Code injection in Fortinet FortiADC, FortiProxy, FortiMail, FortiOS","id":"CVE-2022-22299"},"products":["Fortinet FortiManager, FortiAnalyzer"],"published":"2022-03-01","related":[{"cvss_score":9.4,"headline":"Fortinet Multiple Products Authentication Bypass Using an Alternate Path or Channel","id":"CVE-2026-24858","kev_date_added":"2026-01-27","published":"2026-01-27"},{"cvss_score":9.3,"headline":"Memory corruption in FortiAnalyzer","id":"CVE-2023-25610","kev_date_added":null,"published":"2025-03-24"},{"cvss_score":8.8,"headline":"Server-side request forgery in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2021-32603","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":8.8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer","id":"CVE-2020-12817","kev_date_added":null,"published":"2020-09-24"},{"cvss_score":8,"headline":"Auth bypass in FortiOS","id":"CVE-2024-48886","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":8,"headline":"Cross-site scripting in Fortinet FortiAnalyzer, FortiManager","id":"CVE-2022-39950","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":7.8,"headline":"Command injection in Fortinet FortiManager, FortiAnalyzer, FortiPortal","id":"CVE-2021-26104","kev_date_added":null,"published":"2022-04-06"}],"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":"partial"},"state":"PUBLISHED","updated":"2024-10-22","vendors":["Fortinet"]},"summary":"Attackers can bypass device policies to force password changes for users in FortiAnalyzer and FortiManager, requiring administrators to upgrade to patched versions.","url":"https://insights.sbomify.com/CVE-2022-22300/"}