{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-4573 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-4573 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-4573 is a critical authentication bypass vulnerability in n/a, published on 9 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-4573 and fix it if it is affected.\n\nWhat it is: CVE-2016-4573 is a critical authentication bypass vulnerability in n/a, published on 9 Sep 2016. 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-2016-4573 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2016-4573/ (Markdown: https://insights.sbomify.com/CVE-2016-4573/index.md)","id":"CVE-2016-4573","markdown":"https://insights.sbomify.com/CVE-2016-4573/index.md","name":"CVE-2016-4573","record":{"aliases":["GHSA-3hqg-24jc-82m9"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Fortinet FortiSwitch","requires_auth":"none","summary":"Remote attackers can bypass authentication and gain administrative access on FortiSwitch devices in FortiLink mode by using an empty password for the rest_admin account.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fortiswitch","vendor":"fortinet"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Fortinet FortiSwitch FSW-108D-POE, FSW-124D, FSW-124D-POE, FSW-224D-POE, FSW-224D-FPOE, FSW-248D-POE, FSW-248D-FPOE, FSW-424D, FSW-424D-POE, FSW-424D-FPOE, FSW-448D, FSW-448D-POE, FSW-448D-FPOE, FSW-524D, FSW-524D-FPOE, FSW-548D, FSW-548D-FPOE, FSW-1024D, FSW-1048D, FSW-3032D, and FSW-R-112D-POE models, when in FortiLink managed mode and upgraded to 3.4.1, might allow remote attackers to bypass authentication and gain administrative access via an empty password for the rest_admin account.","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":"Auth bypass in n/a","id":"CVE-2016-4573","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Integer overflow in n/a","id":"CVE-2016-4574"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2016-4572"},"products":["n/a"],"published":"2016-09-09","related":[{"cvss_score":9.6,"headline":"Hardcoded credentials in FortiSwitch","id":"CVE-2023-37936","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":9.3,"headline":"Auth bypass in FortiSwitch","id":"CVE-2024-48887","kev_date_added":null,"published":"2025-04-08"},{"cvss_score":7.6,"headline":"Command injection in FortiSwitch","id":"CVE-2023-37937","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":6.5,"headline":"Denial of service in Fortinet FortiSwitch","id":"CVE-2021-26111","kev_date_added":null,"published":"2021-06-01"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can bypass authentication and gain administrative access on FortiSwitch devices in FortiLink mode by using an empty password for the rest_admin account.","url":"https://insights.sbomify.com/CVE-2016-4573/"}