dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2010-3186

HIGH · 10.0 CVSS v2.0 Published 2010-08-30
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
IBM WebSphere Application Server (WAS) 7.x before 7.0.0.13, and WebSphere Application Server Feature Pack for Web Services 6.1.0.9 through 6.1.0.32, when a JAX-WS application is used, does not properly handle an IncludeTimestamp setting in the WS-Security policy, which has unspecified impact and remote 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

IBM WebSphere Application Server 7.x before 7.0.0.13 and Feature Pack for Web Services 6.1.0.9-6.1.0.32 improperly handles the IncludeTimestamp setting in WS-Security policies when JAX-WS applications are used, allowing remote attackers to exploit the policy handling flaw with unspecified impact.

MitigationUpgrade IBM WebSphere Application Server to version 7.0.0.13 or later, or apply the appropriate fix pack for the Feature Pack for Web Services to address the WS-Security policy IncludeTimestamp handling vulnerability.

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:= 7.0= 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.9= 7.0.0.10= 7.0.0.11= 6.1.0.9

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. Determine installed WebSphere Application Server version
    Run the versionInfo.sh (Unix) or versionInfo.bat (Windows) script from the WebSphere bin directory, or check the About WebSphere Application Server panel in the administrative console
    Affected if The reported version is 7.0.x before 7.0.0.13, or the Feature Pack for Web Services version is between 6.1.0.9 and 6.1.0.32 inclusive
  2. Identify if JAX-WS applications are deployed
    Review deployed applications in the WebSphere administrative console or inspect application deployment descriptors for javax.jws.WebService annotations or JAX-WS web service markup
    Affected if JAX-WS based web services are deployed and active in the environment
  3. Check for WS-Security policy configurations
    Inspect deployed JAX-WS applications for WS-Security policy files (typically in the WEB-INF or META-INF directories) or review WebSphere WS-Security policy configurations in the administrative console under Services > Policy sets
    Affected if WS-Security policies with IncludeTimestamp setting are configured for any application
  4. Verify the policy uses IncludeTimestamp
    Open the WS-Security policy configuration file (commonly named policy.xml or in the binding files) and locate the IncludeTimestamp element within the Timestamp or wsp:Policy element
    Affected if The IncludeTimestamp element is present and set to true or enabled in the WS-Security policy configuration

A user is affected if running WebSphere 7.0.x before 7.0.0.13 or Feature Pack for Web Services 6.1.0.9-6.1.0.32 AND has JAX-WS applications with WS-Security policies that include the IncludeTimestamp setting configured.

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

Upgrade IBM WebSphere Application Server to version 7.0.0.13 or later, or apply the appropriate fix pack for the Feature Pack for Web Services to address the WS-Security policy IncludeTimestamp handling vulnerability.

Recommended fix High confidence

WebSphere Application Server 7.0.0.13 or later (including 7.0.0.14, 7.0.0.15, etc.)

  1. 1. Back up the current WebSphere Application Server configuration and all deployed applications.
  2. 2. Download IBM WebSphere Application Server version 7.0.0.13 or later from IBM Fix Central (fixcentral.ihi.com).
  3. 3. Apply the update using IBM Update Installer for WebSphere Software or IBM Installation Manager, following IBM's standard upgrade procedures.
  4. 4. After upgrading, verify that the IncludeTimestamp setting in WS-Security policies for JAX-WS applications is properly configured according to IBM documentation.
  5. 5. Test all JAX-WS web services applications that use WS-Security to ensure functionality is intact.
  6. 6. Once testing is complete, deploy the updated configuration to production environments.
Caveat Major version upgrades of WebSphere Application Server may introduce compatibility changes with existing applications; thorough testing of all JAX-WS web services is recommended before production deployment.

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

Fix this in Websphere Application Server Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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