CVE-2011-1394
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 Maximo Asset Management and Asset Management Essentials 6.2, 7.1, and 7.5; IBM Tivoli Asset Management for IT 6.2, 7.1, and 7.2; IBM Tivoli Service Request Manager 7.1 and 7.2; IBM Maximo Service Desk 6.2; and IBM Tivoli Change and Configuration Management Database (CCMDB) 6.2, 7.1, and 7.2 allow remote attackers to cause a denial of service (memory consumption) by establishing many UI sessions within one HTTP session.
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 confidenceThe vulnerability allows remote attackers to cause memory exhaustion denial of service by establishing multiple UI sessions within a single HTTP session, leading to uncontrolled memory consumption in affected IBM Maximo and Tivoli products.
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.2= 7.1= 7.5= 6.2= 7.1= 7.5= 6.2= 7.1= 7.2= 7.1= 7.2= 6.2= 6.2= 7.1= 7.2CVSS 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 the installed Maximo or Tivoli product versionAccess the product's About or System Information page in the web UI (typically at /maximo/about.jsp or via Help > System Information in the client), or check the version.xml file in the installation directoryAffected if The installed version is exactly 6.2, 7.1, 7.2, or 7.5 for any of the affected products listed in the CVE (Maximo Asset Management, Maximo Asset Management Essentials, Tivoli Asset Management For IT, Tivoli Service Request Manager, Maximo Service Desk, or Tivoli Change And Configuration Management D
-
Confirm the web UI interface is enabledVerify the IBM HTTP Server and Maximo/Tivoli web application are running. Check if port 80/443 or the configured web port is listening and accessibleAffected if The web UI is exposed and accessible to network users, which is required for the vulnerability to be exploitable
-
Check for session limit configurationInspect the web.xml deployment descriptor in the application (typically under Maximo.ear/maximouiweb.war/WEB-INF/web.xml) or the maximo.properties file for session management settings such as 'mxe.maxsessions' or similar session throttling parametersAffected if Session limit controls are not configured or are set to allow unlimited concurrent UI sessions per HTTP session, leaving the system vulnerable to memory exhaustion from multiple UI session creation
You are affected if you are running any of the listed product versions (6.2, 7.1, 7.2, or 7.5) with the web UI enabled and without configured session limits to restrict multiple UI sessions per HTTP session.
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 patches for the affected products and implement session limits/timeouts to restrict the number of UI sessions per HTTP session and prevent memory exhaustion.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1394 — 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-1394 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