CVE-2011-1322
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 · uneditedThe SOAP with Attachments API for Java (SAAJ) implementation in the Web Services component in IBM WebSphere Application Server (WAS) 6.1.0.x before 6.1.0.37 and 7.x before 7.0.0.15 allows remote attackers to cause a denial of service (memory consumption) via encrypted SOAP messages.
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 confidenceThe SOAP with Attachments API for Java (SAAJ) implementation in IBM WebSphere Application Server 6.1.0.x before 6.1.0.37 and 7.x before 7.0.0.15 contains a vulnerability where specially crafted encrypted SOAP messages can trigger excessive memory consumption, leading to denial of service.
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= 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= 6.1.0.17CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify WebSphere installation and versionRun the WebSphere versionInfo command from the bin directory: versionInfo.sh (Unix) or versionInfo.bat (Windows). Look for the version number in the output under 'Version' and 'Build Level'.Affected if The version shows 6.1.0.x where x is less than 37, or 7.x where x is less than 15 (before 7.0.0.15).
-
Verify the exact build levelCheck the 'Build Level' field from versionInfo output. For 6.1.0.x, look for builds before 6.1.0.37. For 7.x, look for builds before 7.0.0.15.Affected if The build level is below 6.1.0.37 for the 6.1.x line, or below 7.0.0.15 for the 7.x line.
-
Confirm SAAJ SOAP processing is in useReview application configurations or deployed web services to determine if SOAP-based web services using SAAJ are enabled. Check application server logs and deployed WAR/EAR files for SAAJ or SOAP message handlers.Affected if The environment processes encrypted SOAP messages through SAAJ, which is typically enabled by default when SOAP web services are deployed.
You are affected if WebSphere version is 6.1.0.x below 6.1.0.37 or 7.x below 7.0.0.15, and the server processes encrypted SOAP messages via SAAJ.
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 dataUpgrade IBM WebSphere Application Server to version 6.1.0.37 or later (for 6.1.x) or 7.0.0.15 or later (for 7.x) to patch the SAAJ vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1322 — 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-2011-1322 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