Authentication GatewayApplication · Watchguard

CVE-2024-6592

CRITICAL · 9.1 CVSS v3.1 Published 2024-09-25
Fix available
A fix is available. Upgrade to after 12.10.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An incorrect authorization vulnerability in the protocol communication between the WatchGuard Authentication Gateway (aka Single Sign-On Agent) on Windows and the WatchGuard Single Sign-On Client on Windows and MacOS allows an attacker with network access to forge communications to affected components. In the event an attacker has already gained network access, they could exploit this vulnerability to retrieve authenticated usernames and group memberships from the Single Sign-On Agent or send arbitrary account and group information to the Single Sign-On Agent for their host. This vulnerability cannot be used by an attacker to gain access to user credentials.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An incorrect authorization vulnerability exists in the protocol communication between the WatchGuard Authentication Gateway (SSO Agent) and the WatchGuard Single Sign-On Client on Windows and MacOS. This allows an attacker to bypass authentication by exploiting the flawed authorization checks in the SSO communication protocol.

MitigationUpdate the WatchGuard Authentication Gateway to a version beyond 12.10.2, Windows SSO Client beyond 12.7, and MacOS SSO Client beyond 12.5.4 to remediate the authorization bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Authentication GatewayApplication
Affected:<= 12.10.2
Single Sign On ClientApplication
Affected:<= 12.5.4<= 12.7

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify WatchGuard Authentication Gateway version
    Locate the Authentication Gateway SSO Agent installation and retrieve its version number, typically found in program information, installed software list, or via the product's management interface
    Affected if The version is 12.10.2 or lower
  2. Identify WatchGuard SSO Client version on Windows
    Locate the WatchGuard Single Sign-On Client installation on Windows systems and retrieve its version number from installed programs or the client application itself
    Affected if The version is 12.7 or lower on Windows
  3. Identify WatchGuard SSO Client version on MacOS
    Locate the WatchGuard Single Sign-On Client installation on MacOS systems and retrieve its version number from Applications or system profiler
    Affected if The version is 12.5.4 or lower on MacOS
  4. Confirm SSO communication is active
    Verify that the WatchGuard SSO Agent and SSO Client are configured and actively communicating on the network, as the vulnerability only applies when the protocol communication is in use
    Affected if SSO communication is enabled and the component versions are within the affected ranges

You are affected if WatchGuard Authentication Gateway is at version 12.10.2 or lower, or Windows SSO Client is at 12.7 or lower, or MacOS SSO Client is at 12.5.4 or lower, and the SSO communication between these components is active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 12.10.2
Interim mitigation

Update the WatchGuard Authentication Gateway to a version beyond 12.10.2, Windows SSO Client beyond 12.7, and MacOS SSO Client beyond 12.5.4 to remediate the authorization bypass vulnerability.

Fix this in Authentication Gateway Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-6592 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data