CVE-2012-0733
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 Rational AppScan Enterprise 5.x and 8.x before 8.5.0.1, when Integrated Windows authentication is used, allows remote authenticated users to obtain administrative privileges by hijacking a session associated with the service account.
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 confidenceIBM Rational AppScan Enterprise 5.x and 8.x before 8.5.0.1 contains a session hijacking vulnerability when Integrated Windows authentication is enabled. An already-authenticated remote user can hijack a session associated with the service account and obtain administrative privileges, achieving privilege escalation from authenticated user to admin.
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= 5.2= 5.4= 5.5.0= 5.5.0.1= 5.5.0.2= 5.6.0= 5.6.0.3= 8.0.0= 8.0.0.1= 8.0.0.2= 8.0.0.3= 8.0.1CVSS 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
- M
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:S/C:P/I:P/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 installed IBM Rational AppScan Enterprise versionLocate the installed version of Rational AppScan Enterprise in the system or application documentation, about screen, or installation directory version file. Common locations include the product's help menu or registry entries under the IBM installation path.Affected if The installed version is 5.2, 5.4, 5.5.0, 5.5.0.1, 5.5.0.2, 5.6.0, 5.6.0.3, 8.0.0, 8.0.0.1, 8.0.0.2, 8.0.0.3, or 8.1 (versions before 8.5.0.1).
-
Verify if Integrated Windows authentication is configuredAccess the Rational AppScan Enterprise administration console or configuration settings. Look for authentication settings or security configuration panels where Integrated Windows authentication (IWA) option is listed.Affected if Integrated Windows authentication is enabled in the product configuration.
-
Confirm session management configurationReview the security or session management settings within the Rational AppScan Enterprise administration interface to verify how user sessions are handled when Windows authentication is active.Affected if Sessions are managed solely through Integrated Windows authentication without additional session token validation.
You are affected if Rational AppScan Enterprise version is 5.2 through 8.1 (any version before 8.5.0.1) AND Integrated Windows authentication is enabled.
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 to IBM Rational AppScan Enterprise version 8.5.0.1 or later. If immediate upgrade is not feasible, consider disabling Integrated Windows authentication and implementing alternative authentication mechanisms with robust session management controls.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0733 — 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-2012-0733 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