GlobalprotectApplication · Paloaltonetworks
CVE-2021-3057
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 stack-based buffer overflow vulnerability exists in the Palo Alto Networks GlobalProtect app that enables a man-in-the-middle attacker to disrupt system processes and potentially execute arbitrary code with SYSTEM privileges. This issue impacts: GlobalProtect app 5.1 versions earlier than GlobalProtect app 5.1.9 on Windows; GlobalProtect app 5.2 versions earlier than GlobalProtect app 5.2.8 on Windows; GlobalProtect app 5.2 versions earlier than GlobalProtect app 5.2.8 on the Universal Windows Platform; GlobalProtect app 5.3 versions earlier than GlobalProtect app 5.3.1 on Linux.
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 stack-based buffer overflow in Palo Alto Networks GlobalProtect app allows a man-in-the-middle attacker to disrupt system processes and potentially execute arbitrary code with SYSTEM privileges. The vulnerability affects multiple versions across Windows, Linux, and Universal Windows Platform clients.
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.0, <= 5.0.8>= 5.0, <= 5.0.9>= 5.0, <= 5.0.10>= 5.1, <= 5.1.1>= 5.1, < 5.1.9>= 5.1.0, <= 5.1.4>= 5.2, < 5.2.8>= 5.3, < 5.3.1= 5.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify installed GlobalProtect version on WindowsOpen Windows Control Panel > Programs and Features, or run 'wmic product get name,version' in Command Prompt, or check C:\Program Files\Palo Alto Networks\GlobalProtect\ for the executable and right-click to view Properties > Details for versionAffected if Version falls within 5.0.x through 5.0.10, 5.1.x through 5.1.8, 5.2.x through 5.2.7, or 5.3.0
-
Identify installed GlobalProtect version on LinuxRun 'rpm -qa | grep -i globalprotect' for RPM-based distros or 'dpkg -l | grep -i globalprotect' for Debian-based distros, or check /usr/local/GlobalProtect for the installation directoryAffected if Version falls within 5.0.x through 5.0.10, 5.1.x through 5.1.8, 5.2.x through 5.2.7, or 5.3.0
-
Identify installed GlobalProtect version on Windows UWPOpen Windows Store > My Library, or go to Settings > Apps & Features, or check the Microsoft Store purchase history for GlobalProtectAffected if Version falls within 5.2.x through 5.2.7 or 5.3.0
-
Confirm GlobalProtect is actively running or configuredOpen Task Manager and look for 'GlobalProtect.exe' process, or check Services for 'Palo Alto Networks GlobalProtect Service', or look for the system tray icon (red/green shield)Affected if GlobalProtect is installed and the service or process is active/enabled on the system
-
Verify the vulnerability condition: MITM network positionDetermine if the system connects through untrusted networks where an attacker could intercept traffic between the GlobalProtect client and portal/gateway (e.g., public WiFi, compromised network infrastructure)Affected if The system operates on networks where a man-in-the-middle attack is plausible, which is the required attack vector for this flaw
A system is affected if it has any version of GlobalProtect within 5.0.x through 5.3.0 (specific minor versions as listed in the CVE) installed and the service is enabled, with the exploit requiring a man-in-the-middle network position.
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.95.2.85.3.1
Upgrade GlobalProtect app to version 5.1.9 or later (Windows), 5.2.8 or later (Windows/UWP), or 5.3.1 or later (Linux).
GlobalProtect 5.1.9+ (Windows), 5.2.8+ (Windows/UWP), or 5.3.1+ (Linux) depending on platform
- Identify the platform (Windows, Linux, or Universal Windows Platform) where GlobalProtect is installed
- Determine the currently installed GlobalProtect version by checking the application or using system inventory tools
- For Windows: If running version 5.1.x, upgrade to version 5.1.9 or later; if running version 5.2.x, upgrade to version 5.2.8 or later
- For Linux: If running version 5.3.x, upgrade to version 5.3.1 or later
- For Universal Windows Platform: If running version 5.2.x, upgrade to version 5.2.8 or later
- Verify the upgrade was successful by confirming the new version number after installation
- Test that GlobalProtect continues to connect successfully to your PAN-OS gateway after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Globalprotect
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3057 — 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-2021-3057 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