Exposed FortiGate logins and password spraying
The short version: A FortiGate login exposed to the internet lets attackers quietly spray common and already-breached passwords across your accounts until one works — no exploit required, just an exposed login on the firewall that guards your network edge.
What you need to know
There's no CVE here and nothing to patch. The weakness is the combination of exposure and weak authentication: a FortiGate authentication portal (SSL VPN or device login) an attacker can reach, in front of accounts whose passwords may be guessable, reused from another site, or already sitting in a public breach dump.
Password spraying is the technique that turns that combination into a breach. Rather than guess many passwords against one account (which trips lockouts), the attacker tries a few high-probability passwords against many accounts, slowly and quietly.
- How they find it — internet-wide scanning and fingerprinting surface FortiGate portals by their recognizable panel.
- How they use it — automated, low-and-slow spraying with common and previously-breached passwords, staying under lockout thresholds.
- What it leads to — FortiGate sits at the network edge. A working credential can mean access through the firewall — VPN access into the environment or a foothold on the device — and a launch point to expand from.
How serious we see it
Moderate — by default, with honest upside risk. An exposed FortiGate login protected by strong, unique credentials and enforced MFA is a manageable exposure, not an emergency. But the real severity is a function of what's behind the door: this is an edge security appliance, so if any account uses a weak or reused password and MFA isn't enforced, this quietly becomes High — a direct, unauthenticated path through the very device meant to keep attackers out. The reassuring part is that it's entirely in your hands to fix, with no vendor patch required.
What to do
- Enforce MFA on every FortiGate account — the single highest-value control; it defeats spraying even when a password is known.
- Keep the device admin interface off the public internet — restrict management to trusted networks or a VPN, and expose only the services you truly need.
- Limit and monitor failed authentication — rate-limit attempts and alert on spray patterns (many accounts, few passwords, low-and-slow).
- Kill weak and reused passwords — enforce strong, unique credentials and check them against known-breached lists.
- Confirm your exposure first — verify which FortiGate logins are reachable from the internet today.
How BreachRisk sees it
BreachRisk discovers FortiGate portals exposed to the internet the way an attacker would — by crawling and fingerprinting your external footprint — and then, where authorized, goes a step further than a scanner: it safely attempts a bounded, rate-limited authentication check using exposed (breach-corpus) and common credentials, within strict non-disruptive limits rather than a brute-force flood. That's the honest difference between detecting a login and demonstrating whether it actually holds. "We have a FortiGate on the internet" becomes a straight answer: is it defended, or one reused password away from access?