CVE-2020-8262
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 vulnerability in the Pulse Connect Secure / Pulse Policy Secure below 9.1R9 could allow attackers to conduct Cross-Site Scripting (XSS) and Open Redirection for authenticated user web interface.
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 stored Cross-Site Scripting (XSS) and open redirection vulnerability exists in the web interface of Pulse Connect Secure and Pulse Policy Secure gateways. An authenticated attacker can inject malicious scripts or redirect users to arbitrary external sites through the authenticated admin or user web portal.
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= 9.1= 9.1< 9.1< 9.1CVSS 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.
-
Identify the product nameDetermine if the system runs Pulse Connect Secure, Pulse Policy Secure, Ivanti Connect Secure, or Ivanti Policy Secure. Check the product name displayed in the admin web interface or system documentation.Affected if The product is one of these four: Pulse Connect Secure, Pulse Policy Secure, Ivanti Connect Secure, or Ivanti Policy Secure.
-
Determine the installed versionLog into the admin web interface and navigate to the System > Status or About page to view the installed version. Alternatively, check the version displayed on the login page or in the system diagnostic logs.Affected if The installed version is 9.1 (for Ivanti products) or any version lower than 9.1 (for Pulsesecure products).
-
Confirm the admin web interface is enabledAccess the admin portal URL (typically /admin) or the user web portal URL. Verify the interface is accessible and responds.Affected if The web interface is accessible and responds to requests.
-
Verify authentication is configuredCheck if local user accounts, LDAP, or RADIUS authentication realms are configured in the gateway. Review the Authentication > Users or Authentication > Auth Servers sections in the admin interface.Affected if Authentication realms are configured and users can log into the admin or user portal.
The environment is affected if the product is Pulse Connect Secure, Pulse Policy Secure, Ivanti Connect Secure, or Ivanti Policy Secure, and the installed version falls within 9.1 (Ivanti) or below 9.1 (Pulsesecure), with the web interface accessible and authentication enabled.
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 data9.1
Upgrade Pulse Connect Secure and Pulse Policy Secure to version 9.1R9 or later to remediate the XSS and open redirection vulnerabilities.
- Consultation4.0 h
- Implementation4.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 $4,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8262 — 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-8262 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