Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2017-11455


diag.cgi in Pulse Connect Secure 8.2R1 through 8.2R5, 8.1R1 through 8.1R10 and Pulse Policy Secure 5.3R1 through 5.3R5, 5.2R1 through 5.2R8, and 5.1R1 through 5.1R10 allow remote attackers to hijack the authentication of administrators for requests to start tcpdump, related to the lack of anti-CSRF tokens.


Security Impact Summary

This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 8.8, indicating it can be exploited remotely over the network with relatively low complexity though user interaction is required and does not require pre-existing privileges . The vulnerability impacts confidentiality (data exposure), integrity (unauthorized modifications), and availability (service disruption) for affected systems. Impacting 3 products from ivanti, from pulsesecure, from pulsesecure organizations running these solutions should prioritize assessment and patching.

Historical Context

First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.


Published

2017-08-29T15:29:00.660

Last Modified

2025-04-20T01:37:25.860

Status

Deferred

Source

[email protected]

Severity

CVSSv3.0: 8.8 (HIGH)

CVSSv2 Vector

AV:N/AC:M/Au:N/C:P/I:P/A:P

  • Access Vector: NETWORK
  • Access Complexity: MEDIUM
  • Authentication: NONE
  • Confidentiality Impact: PARTIAL
  • Integrity Impact: PARTIAL
  • Availability Impact: PARTIAL
Exploitability Score

8.6

Impact Score

6.4

Weaknesses
  • Type: Primary
    CWE-352

Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application ivanti connect_secure 8.1 Yes
Application pulsesecure pulse_connect_secure 8.1r1.0 Yes
Application pulsesecure pulse_connect_secure 8.2r1.0 Yes
Application pulsesecure pulse_connect_secure 8.2r1.1 Yes
Application pulsesecure pulse_connect_secure 8.2r2.0 Yes
Application pulsesecure pulse_connect_secure 8.2r3.0 Yes
Application pulsesecure pulse_connect_secure 8.2r3.1 Yes
Application pulsesecure pulse_connect_secure 8.2r4.0 Yes
Application pulsesecure pulse_connect_secure 8.2r4.1 Yes
Application pulsesecure pulse_connect_secure 8.2r5.0 Yes
Application pulsesecure pulse_policy_secure 5.1r1.0 Yes
Application pulsesecure pulse_policy_secure 5.1r1.1 Yes
Application pulsesecure pulse_policy_secure 5.1r2.0 Yes
Application pulsesecure pulse_policy_secure 5.1r2.1 Yes
Application pulsesecure pulse_policy_secure 5.1r3.0 Yes
Application pulsesecure pulse_policy_secure 5.1r3.2 Yes
Application pulsesecure pulse_policy_secure 5.1r4.0 Yes
Application pulsesecure pulse_policy_secure 5.1r5.0 Yes
Application pulsesecure pulse_policy_secure 5.1r6.0 Yes
Application pulsesecure pulse_policy_secure 5.1r7.0 Yes
Application pulsesecure pulse_policy_secure 5.1r7.1 Yes
Application pulsesecure pulse_policy_secure 5.1r8.0 Yes
Application pulsesecure pulse_policy_secure 5.1r9.1 Yes
Application pulsesecure pulse_policy_secure 5.1r10 Yes
Application pulsesecure pulse_policy_secure 5.2r1.0 Yes
Application pulsesecure pulse_policy_secure 5.2r2.0 Yes
Application pulsesecure pulse_policy_secure 5.2r3.0 Yes
Application pulsesecure pulse_policy_secure 5.2r3.2 Yes
Application pulsesecure pulse_policy_secure 5.2r4.0 Yes
Application pulsesecure pulse_policy_secure 5.2r5.0 Yes
Application pulsesecure pulse_policy_secure 5.2r6.0 Yes
Application pulsesecure pulse_policy_secure 5.2r7.0 Yes
Application pulsesecure pulse_policy_secure 5.2r7.1 Yes
Application pulsesecure pulse_policy_secure 5.2r8.0 Yes
Application pulsesecure pulse_policy_secure 5.3r1.0 Yes
Application pulsesecure pulse_policy_secure 5.3r1.1 Yes
Application pulsesecure pulse_policy_secure 5.3r2.0 Yes
Application pulsesecure pulse_policy_secure 5.3r3.0 Yes
Application pulsesecure pulse_policy_secure 5.3r3.1 Yes
Application pulsesecure pulse_policy_secure 5.3r4.0 Yes
Application pulsesecure pulse_policy_secure 5.3r4.1 Yes
Application pulsesecure pulse_policy_secure 5.3r5.0 Yes
Application pulsesecure pulse_policy_secure 5.3r5.1 Yes
Application pulsesecure pulse_policy_secure 5.3r5.2 Yes
Application pulsesecure pulse_policy_secure 5.3r6.0 Yes
Application pulsesecure pulse_policy_secure 5.3r7.0 Yes
Application pulsesecure pulse_policy_secure 5.3r8.0 Yes

References

How SecUtils Interprets This CVE

SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For ivanti's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.