Pan OsOperating system · Paloaltonetworks
CVE-2020-1997
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 · uneditedAn open redirection vulnerability in the GlobalProtect component of Palo Alto Networks PAN-OS allows an attacker to specify an arbitrary redirection target away from the trusted GlobalProtect gateway. If the user then successfully authenticates it will cause them to access an unexpected and potentially malicious website. This issue affects: PAN-OS 7.1 versions earlier than 7.1.26; PAN-OS 8.0 versions earlier than 8.0.14.
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 confidenceOpen redirection vulnerability in Palo Alto Networks PAN-OS GlobalProtect component allows attackers to specify an arbitrary redirection target. After successful authentication, users are redirected to attacker-controlled URLs instead of the legitimate GlobalProtect gateway, potentially leading to phishing or malware delivery.
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
Pan OsOperating system
>= 7.1.0, < 7.1.26>= 8.0.0, < 8.0.14CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 is enabledCheck the PAN-OS device dashboard or run 'show global-protect' command in CLI to confirm GlobalProtect portal or gateway is configured and activeAffected if GlobalProtect is deployed and the PAN-OS version falls within the affected ranges
-
Confirm PAN-OS versionRun 'show system info' or check the web interface under Device > Summary to identify the exact PAN-OS version numberAffected if Version is 7.1.0 through 7.1.25, or 8.0.0 through 8.0.13 (not 7.1.26+ or 8.0.14+)
-
Check GlobalProtect portal configurationIn PAN-OS web UI, navigate to GlobalProtect > Portals, or run 'show global-protect portal' CLI command to examine the portal settingsAffected if A portal is configured and the PAN-OS version is in the affected range
The environment is affected if GlobalProtect is actively configured and the PAN-OS version is 7.1.0-7.1.25 or 8.0.0-8.0.13, making users vulnerable to post-authentication open redirection attacks.
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.
From vendor data7.1.268.0.14
Upgrade PAN-OS to version 7.1.26 or later for 7.1 branches, or 8.0.14 or later for 8.0 branches. Schedule maintenance window and ensure configurations are backed up before applying patches.
Fix this in Pan Os
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1997 — 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-2020-1997 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