CVE-2017-17108
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 · uneditedPath traversal vulnerability in the administrative panel in KonaKart eCommerce Platform version 8.7 and earlier could allow an attacker to download system files, as well as upload specially crafted JSP files and in turn gain access to the server.
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 · moderate confidencePath traversal vulnerability in the administrative panel of KonaKart eCommerce Platform versions 8.7 and earlier allows attackers to download arbitrary system files from the server filesystem and upload malicious JSP files, potentially achieving remote code execution and full server compromise.
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.7.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 KonaKart installation and versionLocate the konakart.war or installation directory, check version file (version.xml, MANIFEST.MF, or version.properties typically in the webapp or installation root)Affected if Installed version is 8.7.0.0 or earlier
-
Verify admin panel accessibilityAttempt to access the administrative interface path (typically /konakart/admin or /admin) via HTTP request from an untrusted networkAffected if Admin panel is reachable without IP restriction or authentication barriers
-
Check for exposed admin endpointsReview web server configuration (server.xml, web.xml, or reverse proxy config) to determine if admin routes are exposed to the internet or untrusted networksAffected if Admin panel network access is not restricted to trusted IPs
-
Inspect application logs for path traversal attemptsSearch KonaKart logs (typically in /logs or /tomcat/logs) for patterns like '../', '..\', or suspicious file access patterns in admin functionalityAffected if Logs show directory traversal attempts or unusual file access from admin sessions
-
Review web.xml for file handling servletsExamine the web.xml deployment descriptor in the konakart.war or WEB-INF directory to identify servlets handling file upload/download operations in admin panelAffected if File handling servlets accept user-supplied path parameters without strict validation
A user is affected if they run KonaKart version 8.7.0.0 or earlier with the administrative panel accessible to untrusted networks or users.
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 dataUpgrade to a patched version beyond 8.7; if upgrade is not feasible, restrict admin panel access to trusted IPs only and implement strict input validation on file path parameters to prevent directory traversal.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17108 — 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-17108 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