{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-30305 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-30305 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-30305 is a low-severity vulnerability in Fortinet Fortisandbox, published on 6 Dec 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-30305 and fix it if it is affected.\n\nWhat it is: CVE-2022-30305 is a low-severity vulnerability in Fortinet Fortisandbox, published on 6 Dec 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-30305 in the wild and no public exploit code.\n\nAffected product: Fortinet Fortisandbox. 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-30305/ (Markdown: https://insights.sbomify.com/CVE-2022-30305/index.md)","id":"CVE-2022-30305","markdown":"https://insights.sbomify.com/CVE-2022-30305/index.md","name":"CVE-2022-30305","record":{"aliases":["GHSA-486j-wqfq-g6vq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Fortinet security appliances","requires_auth":"none","summary":"Remote attackers can bypass brute-force protections by entering incorrect credentials without triggering log entries or attempt limits.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"fortinet","cpe":[{"product":"fortideceptor","vendor":"fortinet"},{"product":"fortisandbox","vendor":"fortinet"}],"cvss":{"score":3.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:X/RC:C","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"},{"id":"CWE-778","name":"Insufficient Logging"}],"description":"An insufficient logging [CWE-778] vulnerability in FortiSandbox versions 4.0.0 to 4.0.2, 3.2.0 to 3.2.3 and 3.1.0 to 3.1.5 and FortiDeceptor versions 4.2.0, 4.1.0 through 4.1.1, 4.0.0 through 4.0.2, 3.3.0 through 3.3.3, 3.2.0 through 3.2.2,3.1.0 through 3.1.1 and 3.0.0 through 3.0.2  may allow a remote attacker to repeatedly enter incorrect credentials without causing a log entry, and with no limit on the number of failed authentication attempts.","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 FortiDeceptor","id":"CVE-2022-30305","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"fortinet:fortisandbox","products":["fortinet:fortisandbox"],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in FortiWeb","id":"CVE-2022-30306"},"packages":[],"prev":{"headline":"Cross-site scripting in FortiAnalyzer","id":"CVE-2022-30304"},"products":["FortiDeceptor","FortiSandbox"],"published":"2022-12-06","related":[{"cvss_score":8.8,"headline":"Command injection in Fortinet FortiDeceptor","id":"CVE-2020-29017","kev_date_added":null,"published":"2021-01-14"},{"cvss_score":8.3,"headline":"Missing authorization in FortiDeceptor","id":"CVE-2022-27487","kev_date_added":null,"published":"2023-04-11"},{"cvss_score":8.1,"headline":"Auth bypass in Fortinet FortiDeceptor","id":"CVE-2020-6644","kev_date_added":null,"published":"2020-06-22"},{"cvss_score":8,"headline":"Cross-site scripting in Fortinet FortiDeceptor","id":"CVE-2022-38373","kev_date_added":null,"published":"2022-11-02"},{"cvss_score":6.5,"headline":"Path traversal in Fortinet FortiDeceptor","id":"CVE-2022-30302","kev_date_added":null,"published":"2022-07-18"},{"cvss_score":6,"headline":"Command injection in FortiDeceptor","id":"CVE-2026-25689","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":5.1,"headline":"Cross-site scripting in FortiDeceptor","id":"CVE-2024-35280","kev_date_added":null,"published":"2025-01-15"}],"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":"Remote attackers can bypass brute-force protections by entering incorrect credentials without triggering log entries or attempt limits.","url":"https://insights.sbomify.com/CVE-2022-30305/"}