GlobalprotectApplication · Paloaltonetworks
CVE-2024-5908
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 · uneditedA problem with the Palo Alto Networks GlobalProtect app can result in exposure of encrypted user credentials, used for connecting to GlobalProtect, in application logs. Normally, these application logs are only viewable by local users and are included when generating logs for troubleshooting purposes. This means that these encrypted credentials are exposed to recipients of the application logs.
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 confidenceThe GlobalProtect app improperly logs encrypted user credentials used for VPN connections. These credentials are written to application logs that are viewable by local users and included in troubleshooting bundles shared with support personnel, exposing the encrypted credentials to unintended recipients.
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
>= 5.1, < 5.1.12>= 6.0, < 6.0.8>= 6.1, < 6.1.3>= 6.2, < 6.2.3CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify GlobalProtect installationLocate the GlobalProtect application on the system. Check for the presence of the GlobalProtect client executable or service. On Windows, look in Program Files or Program Files (x86). On macOS, check /Applications. On Linux, check standard application directories or use package management tools.Affected if GlobalProtect is installed and the application is present on the system
-
Determine installed GlobalProtect versionUse system tools to query the installed version. On Windows, check the file properties of the GlobalProtect executable or view installed programs. On macOS, right-click the app and select Get Info. On Linux, check the RPM/DEB package information or run the application with a version flag if available.Affected if The installed version falls within one of the affected ranges: >= 5.1 and < 5.1.12, >= 6.0 and < 6.0.8, >= 6.1 and < 6.1.3, or >= 6.2 and < 6.2.3
-
Locate GlobalProtect application log filesSearch for log directories or files associated with GlobalProtect. Common locations include installation directories, user AppData folders, system logs, or /var/log on Linux. Look for files with .log extensions or log directories named globalprotect, GP, or PAN.Affected if Log files exist and are accessible for reading by local users on the system
-
Inspect logs for credential-related entriesOpen the GlobalProtect log files using a text editor or command-line tools such as grep, less, or tail. Search for patterns that may indicate credential storage, such as references to password, credential, authentication tokens, or encrypted credential strings.Affected if Log files contain entries with encrypted credential data, password strings, or authentication-related information that should not have been logged
The system is affected if GlobalProtect is installed with a version in the affected ranges AND log files containing encrypted credentials are present and readable.
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.126.0.86.1.3
Configure log rotation and access controls to limit who can access application logs. Consider implementing log sanitization to remove sensitive data before sharing logs for troubleshooting. Apply vendor patches when available.
Upgrade to 5.1.12, 6.0.8, 6.1.3, or 6.2.3 (or later) depending on your current major version branch; prefer the latest stable version in your branch
- Identify the currently installed GlobalProtect app version by checking the application or system information
- Determine which version branch you are running (5.1.x, 6.0.x, 6.1.x, or 6.2.x)
- Download the appropriate fixed version from the Palo Alto Networks support portal or official channels: 5.1.12 for 5.1.x branch, 6.0.8 for 6.0.x branch, 6.1.3 for 6.1.x branch, or 6.2.3 for 6.2.x branch
- Install the upgrade following standard Palo Alto Networks GlobalProtect installation procedures
- After upgrade, verify the application logs no longer contain encrypted credentials
- If generating support bundles for troubleshooting, ensure recipients are authorized to handle credential-related data
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
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-5908 — 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-5908 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