CVE-2015-5039
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 Remote Client and change management integrations in IBM Rational ClearCase 7.1.x, 8.0.0.x before 8.0.0.18, and 8.0.1.x before 8.0.1.11 do not properly validate hostnames in X.509 certificates from SSL servers, which allows remote attackers to spoof servers and obtain sensitive information or modify network traffic via a crafted certificate. IBM X-Force ID: 106715.
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 ClearCase's Remote Client and change management integrations fail to properly validate hostnames in X.509 certificates from SSL servers. This allows an attacker with a crafted certificate matching an arbitrary hostname to perform man-in-the-middle attacks, spoofing legitimate servers to intercept or modify sensitive network traffic.
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>= 7.1, <= 7.1.2.16> 8.0, <= 8.0.0.17>= 8.0.1, <= 8.0.1.10CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 installed Rational ClearCase versionRun 'cleartool version' or check the program's About/version information in the ClearCase Administration console. On Windows, this may also appear in Add/Remove Programs.Affected if The version is 7.1.0 through 7.1.2.16, 8.0.0.0 through 8.0.0.17, or 8.0.1.0 through 8.0.1.10.
-
Verify if ClearCase Remote Client (CCRC) is in useCheck if users connect to ClearCase servers via the CCRC WAN server/bridge or through the Web Views feature. Look for 'ccrc' processes or CCRC configuration files on the system.Affected if CCRC is configured and the installed ClearCase version falls within the affected ranges listed above.
-
Check for change management integrationsReview ClearCase integration configurations with external change management tools (such as ClearQuest or third-party systems). Look for .cm_xxx configuration files or registry entries indicating these integrations are active.Affected if Change management integrations are active and the installed version is within the affected ranges.
-
Confirm SSL/TLS connectivity is used with remote serversReview network configuration for ClearCase server connections. Check if HTTPS/SSL is used for CCRC WAN server connections or change management tool interfaces.Affected if SSL/TLS connections are established to remote ClearCase or change management servers, and the version is affected.
You are affected if your installed IBM Rational ClearCase version falls within 7.1.0-7.1.2.16, 8.0.0.0-8.0.0.17, or 8.0.1.0-8.0.1.10 AND you use CCRC or change management integrations over SSL/TLS.
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 ClearCase version 8.0.0.18, 8.0.1.11, or later which contain proper hostname validation in X.509 certificate processing.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.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 $4,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5039 — 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-2015-5039 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