Critical [CVE-2024-55591 +1] Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] affecting FortiOS version 7.0.0 through 7.0.16 and FortiProxy version 7.0.0 through 7.0.19 and 7.2.0 through 7.2.12 allows a remote attacker to gain super-admin privileges via crafted requests to Node.js websocket module
This critical-severity Fortinet advisory covers CVE-2024-55591 and CVE-2025-24472 affecting FortiOS, FortiProxy.
Android app · Google Play
Monitor future Fortinet CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] affecting FortiOS version 7.0.0 through 7.0.16 and FortiProxy version 7.0.0 through 7.0.19 and 7.2.0 through 7.2.12 allows a remote attacker to gain super-admin privileges via crafted requests to Node.js websocket module.
CISA Known Exploited Vulnerability
- Listed:
- Jan 14, 2025 · federal remediation due Jan 21, 2025
- Required action:
- Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Ransomware use:
- Known
KEV is a prioritization signal from CISA — remediation detail still comes from the vendor advisory.
- FortiOS 7.0: 7.0.0 through 7.0.16
- FortiProxy 7.2: 7.2.0 through 7.2.12
- FortiProxy 7.0: 7.0.0 through 7.0.19
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
- FortiOS 7.0: 7.0.17
- FortiProxy 7.2: 7.2.13
- FortiProxy 7.0: 7.0.20
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- Upgrade per the Affected/Solution table: FortiOS 7.0: 7.0.17; FortiProxy 7.2: 7.2.13; FortiProxy 7.0: 7.0.20.
- Disable HTTP/HTTPS administrative interface
- Limit IP addresses that can reach the administrative interface via local-in policies:
- config firewall addressedit "my_allowed_addresses"set subnet end
- Then create an Address Group:
- config firewall addrgrpedit "MGMT_IPs"set member "my_allowed_addresses"end
- Create the Local in Policy to restrict access only to the predefined group on management interface (here: port1):
- config firewall local-in-policyedit 1set intf port1set srcaddr "MGMT_IPs"set dstaddr "all"set action acceptset service HTTPS HTTPset schedule "always"set status enablenext
- edit 2set intf "any"set srcaddr "all"set dstaddr "all"set action denyset service HTTPS HTTPset schedule "always"set status enableend
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.