dbcve.org
Mobile Vpn With SslApplication · Watchguard

CVE-2024-4944

HIGH · 7.8 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 12.10.4 or later.
See remediation →
80/100
Remediation priority · High
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
A local privilege escalation vlnerability in the WatchGuard Mobile VPN with SSL client on Windows enables a local user to execute arbitrary commands with elevated privileged.

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

A local privilege escalation vulnerability in the WatchGuard Mobile VPN with SSL client for Windows allows an unprivileged local user to execute arbitrary commands with elevated SYSTEM-level privileges. The vulnerability stems from improper privilege handling within the VPN client software, enabling a local attacker to escalate their privileges on the affected Windows system.

MitigationApply the vendor-supplied patch or update to WatchGuard Mobile VPN with SSL client to the latest version that addresses CVE-2024-4944. Until the patch is deployed, restrict local access to the affected systems to trusted, privileged users only.

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
Mobile Vpn With SslApplication
Affected:< 12.10.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify if WatchGuard Mobile VPN with SSL is installed
    Open Windows Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*WatchGuard*Mobile*VPN*SSL*'}
    Affected if No entry found means the product is not installed and is not affected
  2. Determine the installed version
    Check the Version or DisplayVersion value in the registry key from step 1, or right-click the executable (typically at C:\Program Files\WatchGuard\Mobile VPN\wgvmvpn.exe) and view Properties > Details
    Affected if Version is present and less than 12.10.4 indicates the installed version is vulnerable
  3. Check if the WatchGuard Mobile VPN service exists and is running
    Open Services console (services.msc) and look for 'WatchGuard Mobile VPN' service, or run: Get-Service -Name '*WatchGuard*' or Get-Service -Name '*wg*'
    Affected if Service exists and is running (required for the privilege escalation to be exploitable)
  4. Verify service executable permissions
    Right-click the service executable (commonly in C:\Program Files\WatchGuard\Mobile VPN\) > Properties > Security tab, or use icacls.exe to view ACLs
    Affected if Non-privileged users have write or modify permissions to the service executable or its directory (indicates easier exploitation path)

The system is affected if WatchGuard Mobile VPN with SSL is installed with a version lower than 12.10.4 and the service is present on the system.

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.

dbcve · scoped
Upgrade available Upgrade to 12.10.4 or later
Fixed in 12.10.4
Interim mitigation

Apply the vendor-supplied patch or update to WatchGuard Mobile VPN with SSL client to the latest version that addresses CVE-2024-4944. Until the patch is deployed, restrict local access to the affected systems to trusted, privileged users only.

Recommended fix High confidence

WatchGuard Mobile VPN with SSL version 12.10.4 or later

  1. Verify the current installed version of WatchGuard Mobile VPN with SSL on the Windows system
  2. Download WatchGuard Mobile VPN with SSL version 12.10.4 or later from the official WatchGuard support portal at www.watchguard.com or through your organization's software distribution channel
  3. Close any active VPN connections before upgrading
  4. Run the installer with appropriate administrative privileges
  5. Follow the on-screen installation prompts to complete the upgrade
  6. Verify the installed version is 12.10.4 or later after installation completes
  7. Test that the Mobile VPN with SSL client functions normally after the upgrade
Caveat Standard upgrade; ensure compatible with your WatchGuard firewall appliance's firmware version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mobile Vpn With Ssl Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-4944 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