dbcve.org
Websphere Application ServerApplication · Ibm

CVE-2010-0776

MEDIUM · 5.0 CVSS v2.0 Published 2010-05-17
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
The Web Container in IBM WebSphere Application Server (WAS) 6.0 before 6.0.2.43, 6.1 before 6.1.0.31, and 7.0 before 7.0.0.11 does not properly handle chunked transfer encoding during a call to response.sendRedirect, which allows remote attackers to cause a denial of service via a GET request.

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 confidence

The Web Container in IBM WebSphere Application Server versions 6.0, 6.1, and 7.0 fails to properly handle chunked transfer encoding when response.sendRedirect is invoked. A remote attacker can send a specially crafted GET request to trigger this condition, causing a denial of service.

MitigationApply the IBM WebSphere patches: upgrade to version 6.0.2.43 or later, 6.1.0.31 or later, or 7.0.0.11 or later. For systems that cannot be patched immediately, consider restricting external access to the Web Container or implementing upstream request filtering.

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.0= 6.0.0.1= 6.0.0.2= 6.0.0.3= 6.0.1= 6.0.1.1= 6.0.1.2= 6.0.1.3= 6.0.1.5= 6.0.1.7= 6.0.1.9= 6.0.1.11

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

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

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
    Run the versionInfo command from the bin directory: versionInfo -short or check the installedPacks file in properties directory
    Affected if Installed version matches 6.0 through 6.0.1.11 (any of the listed affected versions)
  2. Confirm Web Container component is running
    Access the WebSphere admin console or check WebContainer PMI (Performance Monitoring Infrastructure) statistics. From admin console: Monitoring and Tuning > Performance Viewer > Current Activity > WebContainer
    Affected if Web Container is enabled and processing HTTP requests on the affected server version
  3. Verify server is exposed to network
    Check network binding configuration in WebSphere admin console under Servers > Server Types > WebSphere application servers > [server] > Web container settings > Web container transport chains
    Affected if Server has an external-facing HTTP transport chain that accepts remote requests

A server is affected if it runs any WebSphere version 6.0.x through 6.0.1.11 with the Web Container enabled and accessible to network requests that can trigger the chunked transfer encoding issue with sendRedirect.

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

Apply the IBM WebSphere patches: upgrade to version 6.0.2.43 or later, 6.1.0.31 or later, or 7.0.0.11 or later. For systems that cannot be patched immediately, consider restricting external access to the Web Container or implementing upstream request filtering.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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