Exposed Bomgar remote-support logins and password spraying
The short version: A Bomgar remote-support portal exposed to the internet lets attackers quietly spray common and already-breached passwords at your accounts — and because Bomgar is a privileged remote-access tool, a single working credential reaches far beyond one login.
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 remote-support login an attacker can reach, in front of accounts that may use guessable, reused, or already-breached passwords.
Password spraying is the technique that turns that combination into a breach. Instead of guessing many passwords against one account (which trips lockouts), the attacker tries a few high-probability passwords across many accounts, slowly and quietly.
- How they find it — routine internet-wide scanning and web crawling surface exposed Bomgar login portals.
- How they use it — automated, low-and-slow spraying with common and previously-breached passwords, staying under lockout thresholds.
- What it leads to — Bomgar exists to give support staff remote access into systems and networks. A working credential on that tool is not access to one app; it's a foothold with reach, privilege, and a path to expand.
How serious we see it
High — because of what sits behind the door. An exposed login protected by strong, unique credentials and enforced MFA is manageable, not an emergency. But Bomgar is privileged remote-access tooling, so the blast radius of a single compromised account is large: internal reach, elevated privilege, and room to move. If any account uses a weak or reused password and MFA isn't enforced, this is a direct, unauthenticated path to serious access. 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 Bomgar account — the single highest-value control; it defeats spraying even when a password is known.
- Restrict the portal to trusted networks — keep remote-access consoles off the open internet where you can, behind a VPN or IP allow-list.
- 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 whether any Bomgar login is reachable from the internet at all.
How BreachRisk sees it
BreachRisk discovers exposed Bomgar login portals the way an attacker would — by crawling 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 Bomgar portal on the internet" becomes a straight answer: is it defended, or one reused password away from privileged access?