cve.bz

CVE-2020-8206 Improper Authentication

8.1 highEPSS 3.0%

High (8.1). EPSS 3.0% estimated probability of exploitation activity in the next 30 days.

On this page
An improper authentication vulnerability exists in Pulse Connect Secure <9.1RB that allows an attacker with a users primary credentials to bypass the Google TOTP.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
3.0% (unchanged from 3.0% a week ago; 3.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 88th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-8206 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-8206?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-8206?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-8206 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
ivanti:connect_secure9.1
ivanti:connect_secure9.1:r1
ivanti:connect_secure9.1:r2
ivanti:connect_secure9.1:r3
ivanti:connect_secure9.1:r4
ivanti:connect_secure9.1:r4.1
ivanti:connect_secure9.1:r4.2
ivanti:connect_secure9.1:r4.3
ivanti:connect_secure9.1:r5
ivanti:connect_secure9.1:r6
ivanti:connect_secure9.1:r7
pulsesecure:pulse_connect_securethrough 9.0
ivanti:policy_secure9.1
ivanti:policy_secure9.1:r1
ivanti:policy_secure9.1:r2
ivanti:policy_secure9.1:r3
ivanti:policy_secure9.1:r3.1
ivanti:policy_secure9.1:r4
ivanti:policy_secure9.1:r4.1
ivanti:policy_secure9.1:r4.2
ivanti:policy_secure9.1:r5
ivanti:policy_secure9.1:r6
ivanti:policy_secure9.1:r7
pulsesecure:pulse_policy_securethrough 9.0

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON