CVE-2017-11193
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPulse 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCSRF vulnerability in Pulse Connect Secure 8.3R1's diag.cgi allows attackers to trick authenticated administrators into executing network diagnostic commands (ping, traceroute, nslookup, arp, portprobe) against arbitrary IP addresses via malicious web pages. The diag.cgi lacks anti-CSRF tokens or referer validation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 8.3r1.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Pulse Connect Secure versionAccess the admin console or check system information page for the installed Pulse Connect Secure version. Common paths: /admin/ or check the system status page.Affected if Version is exactly 8.3r1.0 (exact match)
-
Verify diag.cgi endpoint existsCheck if the diag.cgi script is present on the device by attempting to access /diag.cgi or reviewing the web interface for network diagnostic tools (ping, traceroute, nslookup, arp, portprobe).Affected if diag.cgi exists and is accessible without additional authentication beyond admin login
-
Check for anti-CSRF token presenceLog into the admin interface, access the diagnostic tools page, and inspect the HTML source or form submissions for a unique CSRF token parameter that changes with each session.Affected if No anti-CSRF token is found in diagnostic tool forms or the same token value is reused across requests
-
Verify Referer/Origin header validationSubmit a diagnostic request from an external/malicious page and observe if the server rejects the request due to missing or invalid Referer/Origin headers.Affected if Server accepts diagnostic requests without validating Referer or Origin headers
-
Confirm admin authentication is activeVerify that an administrator session is currently authenticated to the Pulse Connect Secure admin console.Affected if Authenticated admin session exists while using the diagnostic functionality
User is affected if running exactly version 8.3r1.0 and the diag.cgi diagnostic interface lacks anti-CSRF token protection and Referer/Origin validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement anti-CSRF tokens for all state-changing operations in diag.cgi, validate Origin/Referer headers server-side, and enable SameSite cookie attributes to prevent cross-site request forgery attacks.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11193 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-11193 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data