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.
Why It Matters
Analysis dossierWhy It Matters
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.
Immediate Attention
Yes
Unknown
Risk basis: CISA KEV exploitation signal; HIGH severity; Source-confirmed exploitation or CISA KEV/ransomware metadata
Affected Products & Remediation
3 source-backed productsVendor or catalog guidance (source)
- CISA KEV: Apply updates per vendor instructions.
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Listed
- Exploited (source statement)
- Yes
- Publicly disclosed (source)
- Unknown
CISA required action: Apply updates per vendor instructions.
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed)
Exposure
- Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
Exploitation evidence
- Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Response
- Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure
CISA KEV Record
Apply updates per vendor instructions.
Change History & Source Data
— No recorded material change
- CNA / source
- support@hackerone.com
- Record status · verification
- UPDATED · CISA KEV confirmed
- CPE
- cpe:2.3:a:ivanti:connect_secure:*:*:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:-:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r1:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r2:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r3:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r4:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r4.1:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r4.2:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r4.3:*:*:*:*:*:*, cpe:2.3:a:ivanti:connect_secure:9.1:r5:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2020-8218"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel descLooking up related community queries…