Credential disclosure via sensitive logging
Published Jun 12, 2024 · Updated Aug 9, 2024
Sensitive-data logging in Palo Alto Networks GlobalProtect App allows local users to obtain encrypted user credentials from application logs. The app writes GlobalProtect, LDAP, or Windows usernames and encrypted passwords to PanGPA.log instead of excluding credential material from diagnostic output. Exposure occurs with RADIUS or local-database authentication, with LDAP authentication, or on Windows when Always On user-logon and single sign-on are enabled; local users and troubleshooting-log recipients can read the stored credentials.
Summary
What happened
Sensitive-data logging in Palo Alto Networks GlobalProtect App allows local users to obtain encrypted user credentials from application logs. The app writes GlobalProtect, LDAP, or Windows usernames and encrypted passwords to PanGPA.log instead of excluding credential material from diagnostic output. Exposure occurs with RADIUS or local-database authentication, with LDAP authentication, or on Windows when Always On user-logon and single sign-on are enabled; local users and troubleshooting-log recipients can read the stored credentials.
The record
- CVE
- CVE-2024-5908
- Published
- Jun 12, 2024
- Updated
- Aug 9, 2024
- Vendor
- Palo Alto Networks
- Product
- GlobalProtect App
- Classifications
- CWE-532, CAPEC-150, T1552.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 12, 2024CVE publishedPublication date reported by the CVE source.
- Aug 9, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.1.0 <5.1.12 changes=[{"at":"5.1.12","status":"unaffected"}]
- Affected versionversion=5.1 <5.1.12
- Affected versionversion=6.0.0 <6.0.8
- Affected versionversion=6.0.0 <6.0.8 changes=[{"at":"6.0.8","status":"unaffected"}]
- Affected versionversion=6.1.0 <6.1.3
- Affected versionversion=6.1.0 <6.1.3 changes=[{"at":"6.1.3","status":"unaffected"}]
- Affected versionversion=6.2.0 <6.2.3
- Affected versionversion=6.2.0 <6.2.3 changes=[{"at":"6.2.3","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo