CVE-2017-6614
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 · uneditedA vulnerability in the file-download feature of the web user interface for Cisco FindIT Network Probe Software 1.0.0 could allow an authenticated, remote attacker to download and view any system file by using the affected software. The vulnerability is due to the absence of role-based access control (RBAC) for file-download requests that are sent to the affected software. An attacker could exploit this vulnerability by sending a crafted HTTP request to the affected software. A successful exploit could allow the attacker to download and view any system file by using the affected software. Cisco Bug IDs: CSCvd11628.
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 confidenceIn Cisco FindIT Network Probe Software 1.0.0, the web interface file-download feature lacks role-based access control (RBAC), allowing any authenticated user to request and download arbitrary system files by sending crafted HTTP requests to the affected software.
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= 1.0.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Cisco FindIT Network Probe is installedCheck for the presence of Cisco FindIT Network Probe software on the system. Common locations include C:\Program Files\Cisco\FindIT Network Probe on Windows or /opt/findit/ on Linux. Look for the FindIT Network Probe executable or service.Affected if The software is installed and running on the system
-
Confirm the installed version is 1.0.0Check the installed version of Cisco FindIT Network Probe. On Windows, right-click the application and select Properties > Details, or run 'FindIT Network Probe - Version' from the Help menu. On Linux, check /opt/findit/version or the application About dialog.Affected if The installed version is exactly 1.0.0
-
Verify the web interface is enabled and accessibleCheck if the FindIT web interface service is running by attempting to access https://localhost:8080 or the configured web port (default is 8080). Verify the service is listening on the expected port using 'netstat -an | findstr 8080' on Windows or 'netstat -tuln | grep 8080' on Linux.Affected if The web interface is running and accessible on the network
-
Check for configured user accountsReview the user accounts configured in FindIT Network Probe. Access the web UI admin panel and navigate to User Management or Users settings. Alternatively, check the configuration file (typically stored in the application data directory) for registered users.Affected if At least one user account exists in the system (authentication is required for exploitation, but any authenticated user can exploit this vulnerability)
A system is affected if Cisco FindIT Network Probe version 1.0.0 is installed with its web interface accessible and at least one user account configured, allowing any authenticated user to download arbitrary files.
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 dataApply the Cisco security patch for CSCvd11628. If patching is delayed, restrict network access to the web UI to trusted users only to reduce the attack surface.
- 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-6614 — 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-6614 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