CVE-2017-11193
HighSummary
Pulse Connect Secure 8.3R1 has a CSRF vulnerability in the diag.cgi file, which allows commands like ping, traceroute, and nslookup to be executed. The lack of CSRF protections enables an attacker to run these commands against any IP if they can trick an admin into visiting their malicious page.
Risk Assessment
This vulnerability poses a risk that an attacker could execute unauthorized commands on behalf of an administrator, potentially leading to information disclosure or disruption of service.
Recommendation
It is recommended to implement CSRF protections in the application and to regularly update the software to the latest versions to minimize risk.
Other vulnerabilities in Pulse Connect Secure 8.3R1
See all- CVE-2017-11196High
Pulse Connect Secure 8.3R1 has a CSRF vulnerability in logout.cgi. The logout function of the admin panel is not protected by any CSRF tokens, allowing an attacker to log out a user by tricking them into visiting a malicious web page.
- CVE-2016-4786High
Pulse Connect Secure (PCS) versions 8.2 before 8.2r1, 8.1 before 8.1r3, 8.0 before 8.0r11, and 7.4 before 7.4r13.4 allow remote attackers to cause a denial of service (CPU consumption) via unspecified vectors.
- CVE-2021-22893CriticalActively exploited
Pulse Connect Secure 9.0R3/9.1R1 and higher is vulnerable to an authentication bypass vulnerability exposed by the Windows File Share Browser and Pulse Secure Collaboration features of Pulse Connect Secure that can allow an unauthenticated user to perform remote arbitrary code execution on the Pulse Connect Secure gateway. This vulnerability has been exploited in the wild.
- CVE-2016-4787Critical
Pulse Connect Secure (PCS) versions 8.2 before 8.2r1, 8.1 before 8.1r2, 8.0 before 8.0r10, and 7.4 before 7.4r13.4 allow remote attackers to read sensitive system authentication files in an unspecified directory via unknown vectors.
Original NVD description (English source)
Pulse Connect Secure 8.3R1 has CSRF in diag.cgi. In the panel, the diag.cgi file is responsible for running commands such as ping, ping6, traceroute, traceroute6, nslookup, arp, and Portprobe. These functions do not have any protections against CSRF. That can allow an attacker to run these commands against any IP if they can get an admin to visit their malicious CSRF page.