CVE-2015-1932
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 WebSphere Application Server 7.x before 7.0.0.39, 8.0.x before 8.0.0.11, and 8.5.x before 8.5.5.7 and WebSphere Virtual Enterprise before 7.0.0.7 allow remote attackers to obtain potentially sensitive information about the proxy-server software by reading the HTTP Via header.
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 confidenceIBM WebSphere Application Server and WebSphere Virtual Enterprise expose the HTTP Via header to remote attackers, allowing them to obtain potentially sensitive information about the proxy-server software in use. This information disclosure vulnerability affects versions 7.x before 7.0.0.39, 8.0.x before 8.0.0.11, 8.5.x before 8.5.5.7, and WebSphere Virtual Enterprise before 7.0.0.7.
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<= 7.0.0.6= 7.0.0.1= 7.0.0.2= 7.0.0.3= 7.0.0.4= 7.0.0.5= 7.0.0.6= 7.0.0.7= 7.0.0.8= 7.0.0.9= 7.0.0.10= 7.0.0.11= 7.0.0.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed WebSphere product and versionAccess the WebSphere administration console and navigate to 'About WebSphere Application Server' or check the version.info file in the installation directory (typically in the 'properties' subdirectory)Affected if The installed version is WebSphere Application Server 7.x before 7.0.0.39, 8.0.x before 8.0.0.11, or 8.5.x before 8.5.5.7; OR WebSphere Virtual Enterprise version 7.0.0.6 or earlier
-
Determine if the Via header is exposed in HTTP responsesSend an HTTP request (GET or POST) to the affected WebSphere server and inspect all response headers, specifically looking for a 'Via' headerAffected if The HTTP response includes a 'Via' header containing proxy or server software information, indicating the vulnerability is present and exploitable
-
Verify the WebSphere Virtual Enterprise installation if applicableCheck if WebSphere Virtual Enterprise is installed by examining the installation directory or product-specific files, and note its version if presentAffected if WebSphere Virtual Enterprise version 7.0.0.6 or earlier is installed
You are affected if your installed WebSphere Application Server version is 7.x before 7.0.0.39, 8.0.x before 8.0.0.11, or 8.5.x before 8.5.5.7 (or WebSphere Virtual Enterprise 7.0.0.6 or earlier) AND HTTP responses from the server contain a Via header revealing proxy information.
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 IBM patches (7.0.0.39, 8.0.0.11, 8.5.5.7 for WAS; 7.0.0.7 for WebSphere Virtual Enterprise) or alternatively configure a reverse proxy to strip or suppress the Via header from responses.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1932 — 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-2015-1932 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