CVE-2024-8687
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 · uneditedAn information exposure vulnerability exists in Palo Alto Networks PAN-OS software that enables a GlobalProtect end user to learn both the configured GlobalProtect uninstall password and the configured disable or disconnect passcode. After the password or passcode is known, end users can uninstall, disable, or disconnect GlobalProtect even if the GlobalProtect app configuration would not normally permit them to do so.
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 confidenceA vulnerability in Palo Alto Networks PAN-OS GlobalProtect allows end users to obtain the configured uninstall password and disable/disconnect passcode through the software interface. With these credentials, users can bypass app configuration restrictions and uninstall, disable, or disconnect GlobalProtect even when the configuration would normally prevent such actions.
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>= 8.1.0, < 8.1.25>= 9.0.0, < 9.0.17>= 9.1.0, < 9.1.16>= 10.0.0, < 10.0.12>= 10.1.0, < 10.1.9>= 10.2.0, < 10.2.4= 11.0.0>= 5.1.0, < 5.1.12>= 5.2.0, < 5.2.13>= 6.0.0, < 6.0.7>= 6.1.0, < 6.1.2= 6.2.0all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check PAN-OS version on the applianceAccess the PAN-OS web interface and navigate to Device > Support, or run 'show system info' in the CLI. Look for the System Version field.Affected if The version is 8.1.0 to 8.1.24, 9.0.0 to 9.0.16, 9.1.0 to 9.1.15, 10.0.0 to 10.0.11, 10.1.0 to 10.1.8, 10.2.0 to 10.2.3, or exactly 11.0.0.
-
Check GlobalProtect client version on endpointsOn Windows, open Programs and Features or check C:\Program Files\Palo Alto Networks\GlobalProtect\ for the version. On macOS, run 'pkgutil --info com.paloaltonetworks.GlobalProtect' in Terminal.Affected if The version is 5.1.0 to 5.1.11, 5.2.0 to 5.2.12, 6.0.0 to 6.0.6, 6.1.0 to 6.1.1, or exactly 6.2.0.
-
Check if GlobalProtect is managed by Prisma AccessIn the PAN-OS web interface, navigate to Network > GlobalProtect > Portals. If the portal configuration shows 'Prisma Access' as the gateway type, or if Device > Managed Cloud > Prisma Access shows active configuration, the deployment uses Prisma Access.Affected if GlobalProtect is connected to Prisma Access for gateway or portal services, which affects all versions.
-
Verify if uninstall or disconnect credentials are configuredIn the PAN-OS web interface, go to GlobalProtect > Client Configuration > App. Look for fields labeled 'Uninstall Password', 'Disable/Disconnect Passcode', or similar credential settings under the client settings.Affected if An uninstall password or disable/disconnect passcode is configured in the GlobalProtect client settings.
The environment is affected if PAN-OS is version 8.1.0-8.1.24, 9.0.0-9.0.16, 9.1.0-9.1.15, 10.0.0-10.0.11, 10.1.0-10.1.8, 10.2.0-10.2.3, or 11.0.0; OR GlobalProtect client is version 5.1.0-5.1.11, 5.2.0-5.2.12, 6.0.0-6.0.6, 6.1.0-6.1.1, or 6.2.0; OR Prisma Access is used, and an uninstall password or disable passcode is configured.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.1.125.2.136.0.7
Apply the vendor-supplied PAN-OS security update to address this vulnerability. Review and rotate any exposed uninstall passwords or passcodes, and verify that GlobalProtect configuration restrictions are functioning correctly post-patch.
PAN-OS: 8.1.25, 9.0.17, 9.1.16, or 10.0.12 | GlobalProtect: 5.1.12, 5.2.13, 6.0.7, or 6.1.2
- Identify the exact PAN-OS or GlobalProtect version currently installed on the affected device
- For PAN-OS: Upgrade to 8.1.25 (if on 8.1.x), 9.0.17 (if on 9.0.x), 9.1.16 (if on 9.1.x), or 10.0.12 (if on 10.0.x)
- For GlobalProtect: Upgrade to 5.1.12 (if on 5.1.x), 5.2.13 (if on 5.2.x), 6.0.7 (if on 6.0.x), or 6.1.2 (if on 6.1.x)
- For Prisma Access: Contact Palo Alto Networks support for patch availability since all versions are affected
- After upgrade, verify the vulnerability is remediated by confirming passwords/passcodes are no longer exposed via GlobalProtect
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-8687 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-8687 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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