dbcve.org
GlobalprotectApplication · Paloaltonetworks

CVE-2024-2431

MEDIUM · 5.5 CVSS v3.1 Published 2024-03-13
Fix available
A fix is available. Upgrade to 5.1.12 / 6.0.4 or later.
See remediation →
57/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
An issue in the Palo Alto Networks GlobalProtect app enables a non-privileged user to disable the GlobalProtect app in configurations that allow a user to disable GlobalProtect with a passcode.

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 Palo Alto Networks GlobalProtect app contains an improper access control vulnerability where a non-privileged user can bypass passcode protection to disable the GlobalProtect VPN client. When the configuration allows users to disable GlobalProtect with a passcode, an authenticated but non-privileged attacker can circumvent this security measure and terminate the VPN protection.

MitigationOrganizations should review whether allowing non-privileged users to disable GlobalProtect is necessary; if not, disable this capability. Apply vendor patches when available and restrict the disable functionality to administrative accounts 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
GlobalprotectApplication
Affected:>= 5.1.0, < 5.1.12>= 5.2.0, <= 5.2.13>= 6.0.0, < 6.0.4= 6.1.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify GlobalProtect version
    Open the GlobalProtect app, go to Settings or About to view the version number. Alternatively, check the program's installed version through system utilities (Add/Remove Programs on Windows, or the app's properties).
    Affected if The installed version falls within: 5.1.0 to 5.1.11, 5.2.0 to 5.2.13, 6.0.0 to 6.0.3, or exactly 6.1.0
  2. Confirm passcode protection is configured
    In the GlobalProtect settings or admin portal configuration, locate the option that controls whether a passcode is required to disconnect or disable the VPN client. Verify if passcode protection for disabling is enabled.
    Affected if Passcode protection for disabling GlobalProtect is turned ON - this is the vulnerable configuration
  3. Check if non-privileged users can disable GlobalProtect
    Review the GlobalProtect portal or client configuration settings to determine whether regular (non-admin) users are permitted to disconnect or disable the VPN. Look for user role or permission settings related to disconnect capability.
    Affected if Non-privileged or standard user accounts are permitted to disable the GlobalProtect VPN connection

You are affected if your GlobalProtect version is within the vulnerable ranges (5.1.0-5.1.11, 5.2.0-5.2.13, 6.0.0-6.0.3, or 6.1.0) AND passcode-protected disable is enabled for non-administrative users.

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.4 or later
Fixed in 5.1.126.0.4
Interim mitigation

Organizations should review whether allowing non-privileged users to disable GlobalProtect is necessary; if not, disable this capability. Apply vendor patches when available and restrict the disable functionality to administrative accounts only.

Recommended fix High confidence

GlobalProtect 5.1.12+, 5.2.14+, 6.0.4+, or 6.1.1+ (preferably latest available version in your branch)

  1. 1. Identify the currently installed GlobalProtect version from the affected list.
  2. 2. For users on GlobalProtect 5.1.x (versions 5.1.0-5.1.11): Upgrade to version 5.1.12 or later.
  3. 3. For users on GlobalProtect 5.2.x (versions 5.2.0-5.2.13): Upgrade to version 5.2.14 or later.
  4. 4. For users on GlobalProtect 6.0.x (versions 6.0.0-6.0.3): Upgrade to version 6.0.4 or later.
  5. 5. For users on GlobalProtect 6.1.0: Upgrade to version 6.1.1 or later.
  6. 6. Obtain the upgrade from the Palo Alto Networks support portal or through your organization's software distribution method.
  7. 7. Test the upgrade in a non-production environment first, especially if using the passcode disable feature.
  8. 8. Deploy the upgrade to production systems.
Caveat Review release notes for your specific version upgrade to check for any changes to passcode disable functionality or other behavioral changes

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

Fix this in Globalprotect Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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