dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2011-1377

HIGH · 10.0 CVSS v2.0 Published 2012-01-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The Web Services Security component in the Web Services Feature Pack before 6.1.0.41 for IBM WebSphere Application Server (WAS) 6.1 does not properly handle the enabling of WS-Security for a JAX-WS application, which has unspecified impact and attack vectors.

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

A vulnerability in the Web Services Security component of IBM WebSphere Application Server 6.1 (with Web Services Feature Pack before 6.1.0.41) allows improper handling when enabling WS-Security for JAX-WS applications, leading to potential security bypass or unspecified impact due to faulty security configuration processing.

MitigationApply WebSphere Application Server 6.1 Web Services Feature Pack patch 6.1.0.41 or later, or migrate to a supported WAS version as WAS 6.1 is long end-of-life.

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:= 6.1= 6.1.0= 6.1.0.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.5= 6.1.0.7= 6.1.0.9= 6.1.0.11= 6.1.0.12= 6.1.0.15

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify WebSphere Application Server version
    Check the installed IBM WebSphere Application Server version by reviewing versioninfo or using the wsadmin script: AdminTask.getVersion()
    Affected if Version is 6.1.x or 6.1.0.x (all listed versions are affected)
  2. Confirm Web Services Feature Pack installation
    Verify if the Web Services Feature Pack for WebSphere Application Server 6.1 is installed by checking the installedApps or using the admin console features list
    Affected if The Web Services Feature Pack is installed on WAS 6.1
  3. Determine Web Services Feature Pack version
    Check the version of the installed Web Services Feature Pack - the fix pack level can be found in the product installation directory or via the version report
    Affected if Feature Pack version is before 6.1.0.41 (including unpatched 6.1.0.0 through 6.1.0.15)
  4. Identify JAX-WS applications with WS-Security enabled
    Review the deployment descriptors (web.xml, ibm-webservices-ext.xmi, or ibm-webservices-ext.xml) for JAX-WS applications to see if WS-Security (JAX-WS security) is configured
    Affected if JAX-WS applications have WS-Security explicitly enabled in their configuration

A user is affected if running WebSphere 6.1 with Web Services Feature Pack at version below 6.1.0.41 AND has JAX-WS applications with WS-Security enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply WebSphere Application Server 6.1 Web Services Feature Pack patch 6.1.0.41 or later, or migrate to a supported WAS version as WAS 6.1 is long end-of-life.

Recommended fix High confidence

WebSphere Application Server 6.1.0.41 or later (6.1.x latest fix pack)

  1. Identify all WebSphere Application Server 6.1 installations in the environment using the affected versions (6.1, 6.1.0, 6.1.0.0, 6.1.0.1)
  2. Download IBM WebSphere Application Server version 6.1.0.41 or later from IBM Fix Central (or obtain from IBM support)
  3. Review the Web Services Feature Pack installation and ensure WS-Security configurations for JAX-WS applications are documented before migration
  4. Apply the WebSphere 6.1.0.41 (or latest available 6.1.x fix pack) to each affected installation
  5. After upgrade, verify that WS-Security is properly configured for JAX-WS applications according to IBM documentation
  6. Test all JAX-WS applications that utilize WS-Security to confirm functionality
  7. Monitor IBM security advisories for any subsequent security updates
Caveat WebSphere 6.1 is end-of-life; ensure compatibility of applications with the fix pack level and verify IBM support status for this legacy version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-1377 — 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-2011-1377 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