CVE-2012-0732
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 Enterprise Console client in IBM Rational AppScan Enterprise 5.x and 8.x before 8.5.0.1 does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and obtain sensitive information via a crafted certificate.
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 Enterprise Console client in IBM Rational AppScan Enterprise versions 5.x and 8.x before 8.5.0.1 does not perform X.509 certificate validation on SSL connections, allowing attackers to intercept encrypted communications via a man-in-the-middle attack using forged certificates.
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
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/A:N
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 IBM Rational AppScan Enterprise versionOpen the IBM Rational AppScan Enterprise client or check the program version through Help > About in the Enterprise Console interfaceAffected if The version listed 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.0.1
-
Confirm the Enterprise Console client component is in useVerify that the vulnerable component is the Enterprise Console client (not the scanner or other components). This is typically the client used to connect to the AppScan Enterprise server for managing scans.Affected if The Enterprise Console client is being used to connect to the AppScan Enterprise server over SSL/HTTPS
-
Verify SSL/TLS connectivity is enabledCheck if the Enterprise Console is configured to connect to the server using HTTPS/SSL. This can be confirmed by examining the connection URL or server configuration.Affected if The Enterprise Console connects to the server over HTTPS (port 8443 or similar SSL ports) and certificate validation is not occurring
-
Compare against the fixed versionCheck if the installed version is earlier than 8.5.0.1Affected if The version is 8.0.1 or earlier, or any 5.x version listed in the affected versions
You are affected if you are running IBM Rational AppScan Enterprise versions 5.2 through 8.0.1 and using the Enterprise Console client to connect to the server over SSL/HTTPS connections.
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 8.5.0.1 or later which implements proper X.509 certificate verification. Until upgraded, ensure the Enterprise Console only operates over trusted networks.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0732 — 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-0732 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