CVE-2017-1423
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 Portal 8.5 and 9.0 exposes backend server URLs that are configured for usage by the Web Application Bridge component. IBM X-Force ID: 127476.
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 WebSphere Portal 8.5 and 9.0 contains an information disclosure vulnerability where the Web Application Bridge component exposes backend server URLs that should remain internal. An unauthenticated remote attacker could potentially access these URLs to discover internal infrastructure.
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.5.0.0= 9.0.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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 WebSphere Portal versionLocate the version file in the WebSphere Portal installation directory, typically in the PortalServer/properties/was/product.properties file, or run the versionInfo command from the wp_profile/bin directory: versionInfo.sh (Unix) or versionInfo.bat (Windows)Affected if Version shown is exactly 8.5.0.0 or 9.0.0.0
-
Confirm Web Application Bridge is configuredCheck for Web Application Bridge configuration files in the WebSphere Portal configuration directory, typically under PortalServer/wasCells/cells/wsadmin-actions.xml or search for WAB-related XML configuration files in the wp_profile/config directoryAffected if Web Application Bridge XML configuration files exist and the component is provisioned in the portal configuration
-
Inspect Web Application Bridge proxy rulesReview the Web Application Bridge configuration for proxy rule definitions that map external requests to backend URLs. These are typically stored in the portal-configuration XML files or can be accessed via WebSphere Integrated Solutions Console under Resources > Resource Environment > ProviderAffected if Proxy rules exist that define backend URL mappings accessible through the Web Application Bridge endpoint
-
Verify external accessibility of WAB endpointTest accessing the Web Application Bridge endpoint externally. The typical path is /wab/ followed by the configured proxy path. Attempt to access this endpoint without authentication from an external network locationAffected if The WAB endpoint responds and returns or redirects to backend internal server URLs without requiring authentication
You are affected if running exactly version 8.5.0.0 or 9.0.0.0 AND the Web Application Bridge is enabled with exposed backend URL configurations accessible to unauthenticated 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 dataApply IBM WebSphere Portal security patches for CVE-2017-1423 and review Web Application Bridge configuration to ensure backend URLs are not exposed to unauthenticated users.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1423 — 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-1423 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