dbcve.org
GlobalprotectApplication · Paloaltonetworks

CVE-2022-0019

MEDIUM · 5.5 CVSS v3.1 Published 2022-02-10
Fix available
A fix is available. Upgrade to 5.1.10 / 5.3.2 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 insufficiently protected credentials vulnerability exists in the Palo Alto Networks GlobalProtect app on Linux that exposes the hashed credentials of GlobalProtect users that saved their password during previous GlobalProtect app sessions to other local users on the system. The exposed credentials enable a local attacker to authenticate to the GlobalProtect portal or gateway as the target user without knowing of the target user’s plaintext password. This issue impacts: GlobalProtect app 5.1 versions earlier than GlobalProtect app 5.1.10 on Linux. GlobalProtect app 5.2 versions earlier than and including GlobalProtect app 5.2.7 on Linux. GlobalProtect app 5.3 versions earlier than GlobalProtect app 5.3.2 on Linux. This issue does not affect the GlobalProtect app on other platforms.

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 confidence

The GlobalProtect app on Linux stores hashed user credentials in a manner that allows other local users on the same system to read them. A local attacker with standard user access can obtain these stored credential hashes and use them to authenticate to GlobalProtect portals/gateways as the compromised user without knowing the plaintext password.

MitigationUpgrade GlobalProtect app to version 5.1.10, 5.2.8, or 5.3.2 or later on Linux. Additionally, rotate credentials for users who saved passwords in affected GlobalProtect sessions.

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, < 5.1.10>= 5.2, <= 5.2.7>= 5.3, < 5.3.2

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GlobalProtect is installed on Linux
    Run command: dpkg -l | grep globalprotect or rpm -qa | grep -i globalprotect or which globalprotect
    Affected if GlobalProtect is not installed on the system
  2. Determine installed GlobalProtect version
    Run: globalprotect --version or check /usr/lib/globalprotect/ for version info, or look in package manager listing
    Affected if Version is 5.1.x below 5.1.10, or 5.2.x at 5.2.7 or below, or 5.3.x below 5.3.2
  3. Locate stored credential files
    Search for credential storage files in GlobalProtect user config directories, typically under ~/.config/GlobalProtect/ or /etc/globalprotect/
    Affected if Credential files exist and are readable by any local user (world-readable or group-readable)
  4. Verify file permissions on credential storage
    Run: ls -la on GlobalProtect config directories and files containing 'credential', 'pass', or 'hash' in filenames
    Affected if Files are readable by other local users (permissions show 'r--r--r--' or similar world-readable settings)

A user is affected if GlobalProtect version falls within the vulnerable ranges AND credential storage files are accessible to other local users on the same Linux system.

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.10 / 5.3.2 or later
Fixed in 5.1.105.3.2
Interim mitigation

Upgrade GlobalProtect app to version 5.1.10, 5.2.8, or 5.3.2 or later on Linux. Additionally, rotate credentials for users who saved passwords in affected GlobalProtect sessions.

Recommended fix High confidence

GlobalProtect app 5.1.10, 5.2.8, or 5.3.2 depending on the branch

  1. 1. Identify the current GlobalProtect app version on the Linux system using the package manager or checking the application version.
  2. 2. Determine which upgrade path applies based on the current version: if running 5.1.x, upgrade to 5.1.10; if running 5.2.x, upgrade to 5.2.8; if running 5.3.x, upgrade to 5.3.2.
  3. 3. Obtain the updated GlobalProtect app package from the Palo Alto Networks support portal or official repositories.
  4. 4. Install the fixed version using the Linux package manager (e.g., dpkg -i or rpm -U) with appropriate privileges.
  5. 5. Verify the installed version matches the target fixed release (5.1.10, 5.2.8, or 5.3.2).
  6. 6. Test that the GlobalProtect client functions normally after the update.

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

Fix this in Globalprotect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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