CVE-2018-1917
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 · uneditedIBM InfoSphere Information Server 11.3, 11.5, and 11.7 could allow an authenticated user to access JSP files and disclose sensitive information. IBM X-Force ID: 152784.
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 confidenceIBM InfoSphere Information Server versions 11.3, 11.5, and 11.7 contain an improper access control vulnerability where authenticated users can access JSP files directly through the web server, potentially exposing sensitive information such as credentials, configuration details, or source code embedded in those files.
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= 11.3= 11.5= 11.7= 11.5= 11.7CVSS 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.
-
Identify installed IBM InfoSphere Information Server versionCheck the product version through the IBM InfoSphere installation directory, version file, or administrative console. Common locations include installation logs, version.info files, or the IIR_HOME environment variable.Affected if The installed version is 11.3, 11.5, or 11.7 (or 11.5/11.7 for On Cloud).
-
Determine if web tier is enabledVerify whether the IBM InfoSphere web tier (web application server) is running and accessible. This is typically hosted on WebSphere Application Server or IIS with WebSphere plugin.Affected if The web tier is enabled and accessible via HTTP/HTTPS.
-
Test direct JSP file accessAttempt to access common JSP file paths through the web server, such as /<application>/*.jsp or /iis/*.jsp. Use a web browser or curl to request JSP files directly without authentication.Affected if JSP files are served directly and return content (source code or processed output) without requiring authentication.
-
Inspect web server configuration for JSP handlingReview the web server configuration (httpd.conf for Apache, plugin-cfg.xml for WebSphere, or IIS configuration) to verify if JSP file types are mapped to be accessible without proper authorization controls.Affected if JSP MIME types or handlers are configured to serve files without authentication or authorization filters.
You are affected if you run IBM InfoSphere Information Server version 11.3, 11.5, or 11.7 with the web tier enabled and JSP files are accessible directly through the web server without authentication.
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 dataRestrict access to JSP files by implementing proper authentication and authorization controls at the web server or application level. Review and remove any sensitive information from JSP files accessible via the web tier.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1917 — 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-2018-1917 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