{"answers":{"affected":"It affects 1 product.","exploited":"Yes. Attackers have exploited CVE-2020-12812 in the wild since at least 3 Nov 2021, including in ransomware campaigns.","fix":"No fix has been published for CVE-2020-12812 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.","what":"CVE-2020-12812 is a high-severity authentication bypass vulnerability in Fortinet Fortios, published on 24 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-12812 and fix it if it is affected.\n\nWhat it is: CVE-2020-12812 is a high-severity authentication bypass vulnerability in Fortinet Fortios, published on 24 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: Yes. Attackers have exploited CVE-2020-12812 in the wild since at least 3 Nov 2021, including in ransomware campaigns.\n\nAffected product: Fortinet Fortios. 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-2020-12812/ (Markdown: https://insights.sbomify.com/CVE-2020-12812/index.md)","id":"CVE-2020-12812","markdown":"https://insights.sbomify.com/CVE-2020-12812/index.md","name":"CVE-2020-12812","record":{"aliases":["GHSA-r9cj-q2hj-hfq9"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet FortiOS","requires_auth":"none","summary":"Attackers can bypass two-factor authentication in FortiOS SSL VPN by changing the case of their username, allowing unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortios","vendor":"fortinet"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"An improper authentication vulnerability in SSL VPN in FortiOS 6.4.0, 6.2.0 to 6.2.3, 6.0.9 and below may result in a user being able to log in successfully without being prompted for the second factor of authentication (FortiToken) if they changed the case of their username.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"exploited"},"has_fix":null,"headline":"Fortinet FortiOS SSL VPN Improper Authentication","id":"CVE-2020-12812","indexable":true,"kev":{"dateAdded":"2021-11-03","dueDate":"2022-05-03","knownRansomwareCampaignUse":"Known","product":"FortiOS","requiredAction":"Apply updates per vendor instructions.","vendorProject":"Fortinet","vulnerabilityName":"Fortinet FortiOS SSL VPN Improper Authentication Vulnerability"},"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortios","products":["fortinet:fortios"],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Fortinet FortiAnalyzer","id":"CVE-2020-12814"},"packages":[],"prev":{"headline":"Cross-site scripting in FortiAnalyzer","id":"CVE-2020-12811"},"products":["Fortinet FortiOS"],"published":"2020-07-24","related":[{"cvss_score":9.8,"headline":"Fortinet Multiple Products Format String","id":"CVE-2024-23113","kev_date_added":"2024-10-09","published":"2024-02-15"},{"cvss_score":9.8,"headline":"Fortinet Multiple Products Authentication Bypass","id":"CVE-2022-40684","kev_date_added":"2022-10-11","published":"2022-10-18"},{"cvss_score":9.6,"headline":"Fortinet FortiOS and FortiProxy Authentication Bypass","id":"CVE-2024-55591","kev_date_added":"2025-01-14","published":"2025-01-14"},{"cvss_score":9.6,"headline":"Fortinet FortiOS Out-of-Bound Write","id":"CVE-2024-21762","kev_date_added":"2024-02-09","published":"2024-02-09"},{"cvss_score":9.3,"headline":"Fortinet FortiOS Heap-Based Buffer Overflow","id":"CVE-2022-42475","kev_date_added":"2022-12-13","published":"2023-01-02"},{"cvss_score":9.2,"headline":"Fortinet FortiOS and FortiProxy SSL-VPN Heap-Based Buffer Overflow","id":"CVE-2023-27997","kev_date_added":"2023-06-13","published":"2023-06-13"},{"cvss_score":9.1,"headline":"Fortinet Multiple Products Improper Verification of Cryptographic Signature","id":"CVE-2025-59718","kev_date_added":"2025-12-16","published":"2025-12-09"}],"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":"open","licence":"CC0 1.0","name":"CISA KEV"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"active","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["n/a"]},"summary":"Attackers can bypass two-factor authentication in FortiOS SSL VPN by changing the case of their username, allowing unauthorized access.","url":"https://insights.sbomify.com/CVE-2020-12812/"}