CVE-2012-0735
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 does not properly scan file: URLs, which allows man-in-the-middle attackers to obtain sensitive information or possibly have unspecified other impact via a crafted URI.
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 confidenceIBM Rational AppScan Enterprise versions 5.x and 8.x before 8.5.0.1 fails to properly scan file: URLs during security assessments. This scanning flaw allows a man-in-the-middle attacker intercepting scan traffic to obtain sensitive information via crafted URIs, as the scanner does not validate or handle these URLs securely.
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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/Au:N/C:C/I:C/A:C
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.
-
Locate installed IBM Rational AppScan Enterprise versionOpen the AppScan Enterprise client and navigate to Help > About, or check the version displayed on the Enterprise Console login screenAffected if The displayed 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.0
-
Verify edition is AppScan EnterpriseConfirm the installed product is IBM Rational AppScan Enterprise specifically, as other AppScan editions may have different version schemesAffected if The product is not IBM Rational AppScan Enterprise (e.g., AppScan Standard)
-
Confirm version is below 8.5.0.1Compare your identified version against the fixed release 8.5.0.1 - any version prior to this build is affectedAffected if The installed version is any 5.x or 8.x release earlier than 8.5.0.1
If IBM Rational AppScan Enterprise is installed at version 5.2, 5.4, 5.5.0.x, 5.6.0.x, 8.0.0.x through 8.1.0, or any other 5.x or 8.x version below 8.5.0.1, the environment is affected by CVE-2012-0735
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 Rational AppScan Enterprise to version 8.5.0.1 or later. Additionally, protect scan traffic by using TLS and network segmentation to prevent MITM attacks during scanning operations.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0735 — 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-0735 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