dbcve.org
GlobalprotectApplication · Paloaltonetworks

CVE-2024-5915

HIGH · 7.8 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 6.1.5 / 6.2.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 privilege escalation (PE) vulnerability in the Palo Alto Networks GlobalProtect app on Windows devices enables a local user to execute programs with elevated privileges.

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

This is a local privilege escalation vulnerability in the Palo Alto Networks GlobalProtect VPN client for Windows. A local, unprivileged user can exploit this flaw to execute arbitrary code or programs with elevated (administrator or SYSTEM) privileges on the affected Windows device.

MitigationApply the vendor-supplied patch or update to the GlobalProtect app to the fixed version specified in Palo Alto Networks security advisory.

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.9>= 6.0.0, <= 6.0.6>= 6.1.0, < 6.1.5>= 6.2.0, < 6.2.4= 6.3.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
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 GlobalProtect is installed
    Check for GlobalProtect installation by looking in Program Files, or checking the Windows Services list for 'GlobalProtect' service, or checking registry key HKLM\SOFTWARE\PaloAltoNetworks\GlobalProtect
    Affected if GlobalProtect client is not found on the system, the vulnerability does not apply
  2. Find installed GlobalProtect version
    Open Programs and Features in Control Panel and find GlobalProtect entry, or right-click the GlobalProtect.exe executable (typically in C:\Program Files\Palo Alto Networks\GlobalProtect\) and select Properties > Details to view the File Version
    Affected if Unable to determine the version number for comparison
  3. Compare version against affected ranges
    Compare your installed version number to these affected ranges: 5.1.0-5.1.9, 6.0.0-6.0.6, 6.1.0-6.1.4, 6.2.0-6.2.3, or 6.3.0 exactly
    Affected if The installed version falls within any of these ranges: 5.1.0 to 5.1.9, 6.0.0 to 6.0.6, 6.1.0 to 6.1.4, 6.2.0 to 6.2.3, or is exactly version 6.3.0

The system is affected if the GlobalProtect VPN client for Windows is installed and the installed version matches one of the vulnerable version ranges listed above.

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 6.1.5 / 6.2.4 or later
Fixed in 6.1.56.2.4
Interim mitigation

Apply the vendor-supplied patch or update to the GlobalProtect app to the fixed version specified in Palo Alto Networks security advisory.

Recommended fix High confidence

Upgrade to GlobalProtect 5.1.10+ (for 5.1.x), 6.0.7+ (for 6.0.x), 6.1.5 (for 6.1.x), or 6.2.4 (for 6.2.x)

  1. Identify the currently installed GlobalProtect version from Add/Remove Programs or the app's About section
  2. Based on the current version, upgrade to the fixed release: For 5.1.0-5.1.9, upgrade to 5.1.10 or later; For 6.0.0-6.0.6, upgrade to 6.0.7 or later; For 6.1.0-6.1.4, upgrade to 6.1.5; For 6.2.0-6.2.3, upgrade to 6.2.4
  3. Download the update from the Palo Alto Networks Customer Support Portal or through your organization's software distribution method
  4. Apply the update with local administrator privileges if required
  5. Verify the update was successful by checking the GlobalProtect version after installation
Caveat Major version jumps (e.g., 5.1 to 6.0) may introduce UI changes or require configuration review; test in 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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