# CVE-2017-11193: Cross-site request forgery in n/a

> An attacker can force an admin to execute network diagnostic commands via CSRF, potentially leading to command execution or security bypass.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c6vq-95h3-7xfg

## What is CVE-2017-11193?

CVE-2017-11193 is a high-severity vulnerability in Pulsesecure Pulse Connect Secure, published on 12 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-11193?

It affects 1 product.


Products: Pulsesecure Pulse Connect Secure.

## How do I fix CVE-2017-11193?

No fix has been published for CVE-2017-11193 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-11193 being exploited?

There is no known exploitation of CVE-2017-11193 in the wild and no public exploit code.

## Other vulnerabilities in Pulsesecure Pulse Connect Secure

- [CVE-2018-5299](https://insights.sbomify.com/CVE-2018-5299/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-11580](https://insights.sbomify.com/CVE-2020-11580/): Security feature bypass in n/a (critical 9.1)
- [CVE-2020-11582](https://insights.sbomify.com/CVE-2020-11582/): Other in n/a (high 8.8)
- [CVE-2017-11196](https://insights.sbomify.com/CVE-2017-11196/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-11581](https://insights.sbomify.com/CVE-2020-11581/): Command injection in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11193 and fix it if it is affected.

What it is: CVE-2017-11193 is a high-severity vulnerability in Pulsesecure Pulse Connect Secure, published on 12 Jul 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-11193 in the wild and no public exploit code.

Affected product: Pulsesecure Pulse Connect Secure. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11193/ (Markdown: https://insights.sbomify.com/CVE-2017-11193/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11193
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11193
- OSV: https://osv.dev/vulnerability/CVE-2017-11193

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11193/
Summaries are generated and may contain mistakes; the official description above is the record.