# CVE-2022-0018: Information disclosure in GlobalProtect App > Local user credentials may be inadvertently sent to the GlobalProtect portal when Single Sign-On is enabled with mismatched credentials, exposing sensitive data. - **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 10 Feb 2022 - **Updated:** 16 Sep 2024 - **Also known as:** GHSA-rvgp-9v6m-x4g4 ## What is CVE-2022-0018? CVE-2022-0018 is a medium-severity vulnerability in Palo Alto Networks GlobalProtect App, published on 10 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description An information exposure vulnerability exists in the Palo Alto Networks GlobalProtect app on Windows and MacOS where the credentials of the local user account are sent to the GlobalProtect portal when the Single Sign-On feature is enabled in the GlobalProtect portal configuration. This product behavior is intentional and poses no security risk when connecting to trusted GlobalProtect portals configured to use the same Single Sign-On credentials both for the local user account as well as the GlobalProtect login. However when the credentials are different, the local account credentials are inadvertently sent to the GlobalProtect portal for authentication. A third party MITM type of attacker cannot see these credentials in transit. This vulnerability is a concern where the GlobalProtect app is deployed on Bring-your-Own-Device (BYOD) type of clients with private local user accounts or GlobalProtect app is used to connect to different organizations. Fixed versions of GlobalProtect app have an app setting to prevent the transmission of the user's local user credentials to the target GlobalProtect portal regardless of the portal configuration. This issue impacts: GlobalProtect app 5.1 versions earlier than GlobalProtect app 5.1.10 on Windows and MacOS; GlobalProtect app 5.2 versions earlier than GlobalProtect app 5.2.9 on Windows and MacOS This issue does not affect GlobalProtect app on other platforms. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-201 (Insertion of Sensitive Information Into Sent Data) ## Which versions are affected by CVE-2022-0018? It affects 1 product. Products: Paloaltonetworks Globalprotect. ## How do I fix CVE-2022-0018? No fix has been published for CVE-2022-0018 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-0018 being exploited? There is no known exploitation of CVE-2022-0018 in the wild and no public exploit code. ## Other vulnerabilities in Palo Alto Networks GlobalProtect App - [CVE-2025-4232](https://insights.sbomify.com/CVE-2025-4232/): GlobalProtect: Authenticated Code Injection Through Wildcard on macOS (high 8.5) - [CVE-2021-3057](https://insights.sbomify.com/CVE-2021-3057/): GlobalProtect App: Buffer Overflow Vulnerability When Connecting to Portal or Gateway (high 8.1) - [CVE-2023-0009](https://insights.sbomify.com/CVE-2023-0009/): GlobalProtect App: Local Privilege Escalation (PE) Vulnerability (high 7.8) - [CVE-2022-0016](https://insights.sbomify.com/CVE-2022-0016/): GlobalProtect App: Privilege Escalation Vulnerability When Using Connect Before Logon (high 7.4) - [CVE-2025-0120](https://insights.sbomify.com/CVE-2025-0120/): GlobalProtect App: Local Privilege Escalation (PE) Vulnerability (high 7.1) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-0018 and fix it if it is affected. What it is: CVE-2022-0018 is a medium-severity vulnerability in Palo Alto Networks GlobalProtect App, published on 10 Feb 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2022-0018 in the wild and no public exploit code. Affected product: Palo Alto Networks GlobalProtect App. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-0018/ (Markdown: https://insights.sbomify.com/CVE-2022-0018/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0018 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0018 - OSV: https://osv.dev/vulnerability/CVE-2022-0018 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-0018/ Summaries are generated and may contain mistakes; the official description above is the record.