dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2005-1112

MEDIUM · 5.0 CVSS v2.0 Published 2005-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
IBM WebSphere Application Server 6.0 and earlier, when sharing the document root of the web server, allows remote attackers to obtain the source code for Java Server Pages (.jsp) via an HTTP request with an invalid Host header, which causes the page to be processed by the web server instead of the JSP engine.

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 confidence

In IBM WebSphere Application Server 6.0 and earlier when sharing the document root with a web server, sending an HTTP request with an invalid Host header causes the web server to serve the raw .jsp file content instead of passing it to the JSP engine for execution. This allows remote attackers to obtain the source code of Java Server Pages, potentially exposing sensitive application logic, credentials, or configuration details.

MitigationEnsure the web server is not configured to serve .jsp files directly from the document root, or configure the web server to deny access to .jsp files, or upgrade to a patched version of WebSphere Application Server.

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
Websphere Application ServerApplication
Affected:= 5.0= 5.0.1= 5.0.2= 5.0.2.1= 5.0.2.3= 5.0.2.4= 5.0.2.5= 5.0.2.6= 5.0.2.7= 5.0.2.8= 5.0.2.9= 5.1.0

CVSS 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
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WebSphere Application Server version
    Run 'about' command in wsadmin or check the installation directory for version file. In WebSphere 5.x, check the product.version property in install_root/properties/was.properties
    Affected if The installed version is one of: 5.0, 5.0.1, 5.0.2, 5.0.2.1, 5.0.2.3, 5.0.2.4, 5.0.2.5, 5.0.2.6, 5.0.2.7, 5.0.2.8, 5.0.2.9, or 5.1.0
  2. Check if document root is shared with a web server
    Examine the web server configuration (httpd.conf for Apache/IHS, or IBM HTTP Server config) to determine if the document root path matches or overlaps with the WebSphere application deployment directory
    Affected if The web server document root is configured to serve files from the same directory tree where JSP files are deployed
  3. Inspect web server MIME types configuration
    Review the web server configuration file for MIME type handlers. Look for AddType or MIME type mappings that associate .jsp files with a plain text or source code content type rather than executing them through the servlet engine
    Affected if The web server is configured to serve .jsp files as static content (text/plain, application/octet-stream) instead of passing them to the WebSphere JSP servlet
  4. Test for source code disclosure
    Send an HTTP request to a known JSP file using a malformed or invalid Host header, such as 'GET /application/file.jsp HTTP/1.1' with 'Host: invalidhost' header, and observe if raw JSP source code is returned instead of executed output
    Affected if The response contains unexecuted JSP source code (visible scriptlets, Java code, or JSP directives) rather than HTML output from the executed page

A system is affected if it runs WebSphere 5.0 through 5.1.0, shares its document root with a web server, and returns raw JSP source code when queried with an invalid Host header.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Ensure the web server is not configured to serve .jsp files directly from the document root, or configure the web server to deny access to .jsp files, or upgrade to a patched version of WebSphere Application Server.

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2005-1112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2005-1112 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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