LiveActive security incident?Get immediate response
CVE Record

CVE-2020-8218: A code injection vulnerability exists in Pulse Connect Secure <9.1R8 that allows an attacker to crafted a U...

A code injection vulnerability exists in Pulse Connect Secure <9.1R8 that allows an attacker to crafted a URI to perform an arbitrary code execution via the admin web interface.

HighCVSS 7.2Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-8218 is a high-severity code injection flaw in Pulse Connect Secure before 9.1R8. A highly privileged attacker could use the admin web interface to execute arbitrary code. Because CISA lists it in KEV, treat unpatched internet-reachable appliances as urgent exposure.

Executive priority

Prioritize remediation now for any exposed or unverified Pulse Connect Secure appliance. KEV status means this is not theoretical risk, and successful exploitation could affect confidentiality, integrity, and availability of a perimeter access system.

Technical view

The CVE describes CWE-94 code injection via a crafted URI against the Pulse Connect Secure admin web interface. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction, with high confidentiality, integrity, and availability impact. Sources state it is fixed in 9.1R8.

Likely exposure

Exposure is most likely where Pulse Connect Secure versions earlier than 9.1R8 remain deployed, especially if the admin web interface is reachable over a network path available to attackers or compromised administrators.

Exploitation context

CISA KEV inclusion supports known exploitation. The provided CVSS vector requires high privileges, so this is not described as unauthenticated access in the source bundle. Public analysis exists, but this assessment does not provide exploit mechanics.

Researcher notes

Evidence supports Pulse Connect Secure before 9.1R8, CWE-94, admin web interface code injection, and high-privilege precondition. The source bundle does not establish unauthenticated exploitation or name compensating controls beyond vendor guidance and the fixed version.

Mitigation direction

  • Upgrade Pulse Connect Secure to 9.1R8 or later per vendor guidance.
  • Restrict admin web interface access to trusted management networks.
  • Review vendor advisory SA44516 for any additional required actions.
  • Audit privileged administrator accounts for compromise or misuse.
  • Monitor administrative interface logs for unusual URI patterns or sessions.

Validation and detection

  • Inventory all Pulse Connect Secure appliances and record running versions.
  • Confirm no appliance remains below 9.1R8.
  • Verify admin web interfaces are not broadly internet reachable.
  • Review administrative access logs around suspicious sessions.
  • Check CISA KEV and vendor advisory status for remediation expectations.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-94: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-8218 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.2 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.2High
CVSS 3.1 vector shape for CVE-2020-8218Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aPulse Connect SecureFixed in 9.1R8Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-94 · source CWE mapping

Improper Control of Generation of Code ('Code Injection')

Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.