dbcve.org
GlobalprotectApplication · Paloaltonetworks

CVE-2024-2432

HIGH · 7.0 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 5.1.12 / 6.0.8 or later.
See remediation →
72/100
Remediation priority · Elevated
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 privilege escalation (PE) vulnerability in the Palo Alto Networks GlobalProtect app on Windows devices enables a local user to execute programs with elevated privileges. However, execution requires that the local user is able to successfully exploit a race condition.

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 · moderate confidence

The GlobalProtect app on Windows contains a local privilege escalation vulnerability where an authenticated local user can exploit a race condition to execute arbitrary code with elevated (SYSTEM) privileges. This enables a non-privileged Windows user to gain full administrative control over the affected device.

MitigationApply the vendor patch for CVE-2024-2432 to the GlobalProtect app; until patched, limit local user access and monitor for suspicious process activity originating from GlobalProtect components.

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
GlobalprotectApplication
Affected:>= 5.1.0, < 5.1.12>= 6.0.0, < 6.0.8>= 6.1.0, < 6.1.2= 6.2.0

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

CVSS:3.1/AV:L/AC:H/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 GlobalProtect installation
    Check for GlobalProtect installation by searching for the program in Windows Registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\) or by looking for the executable at C:\Program Files\Palo Alto Networks\GlobalProtect\
    Affected if GlobalProtect is not installed on the system
  2. Determine installed GlobalProtect version
    Open Programs and Features in Control Panel, find Palo Alto GlobalProtect, and note the version column; or run 'msiexec /x {product-code} /qn /liwear log.txt' to extract version from Windows Installer logs; or check version info on PanGPA.dll in the GlobalProtect installation directory
    Affected if Unable to determine the installed version from available sources
  3. Compare version against affected ranges
    Match the discovered version number against the vulnerable ranges: 5.1.0 through 5.1.11, 6.0.0 through 6.1.2, or exactly 6.2.0
    Affected if Installed version falls within >= 5.1.0 and < 5.1.12, OR >= 6.0.0 and < 6.0.8, OR >= 6.1.0 and < 6.1.2, OR equals 6.2.0
  4. Confirm GlobalProtect service status
    Open Services console (services.msc) and check if the GlobalProtect service is running, or run 'sc query GlobalProtect' from command prompt
    Affected if GlobalProtect service is currently running (exploitation requires the vulnerable service to be active)

A system is affected if GlobalProtect is installed with a version matching any of the vulnerable ranges (5.1.0-5.1.11, 6.0.0-6.0.7, 6.1.0-6.1.1, or 6.2.0) and the service is actively running.

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 5.1.12 / 6.0.8 / 6.1.2 or later
Fixed in 5.1.126.0.86.1.2
Interim mitigation

Apply the vendor patch for CVE-2024-2432 to the GlobalProtect app; until patched, limit local user access and monitor for suspicious process activity originating from GlobalProtect components.

Recommended fix Moderate confidence

GlobalProtect 5.1.12 (or later), 6.0.8 (or later), 6.1.2 (or later), or 6.2.1+ - choose the minimum fixed version for your current branch

  1. Identify the currently installed GlobalProtect version on Windows devices using the Add/Remove Programs list or the GlobalProtect UI (Settings > About)
  2. Determine which version branch the installed GlobalProtect belongs to (5.1.x, 6.0.x, 6.1.x, or 6.2.0)
  3. Download the appropriate fixed version from the Palo Alto Networks Customer Support Portal or software downloads page: 5.1.12 for 5.1.x branches, 6.0.8 for 6.0.x branches, 6.1.2 for 6.1.x branches, and 6.2.1 or later for 6.2.0
  4. Close all running applications and ensure no active GlobalProtect connections are in use
  5. Run the GlobalProtect installer with administrator privileges
  6. Follow the on-screen installation wizard prompts to complete the upgrade
  7. Restart the Windows device if prompted by the installer
  8. Verify the installed GlobalProtect version matches the expected fixed version after upgrade
Caveat Upgrading GlobalProtect may require re-authentication and potential reconfiguration of VPN settings; test in a non-production environment first

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

Fix this in Globalprotect Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-2432 — 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-2432 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