CVE-2018-5761
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 · uneditedA man-in-the-middle vulnerability related to vCenter access was found in Rubrik CDM 3.x and 4.x before 4.0.4-p2. This vulnerability might expose Rubrik user credentials configured to access vCenter as Rubrik clusters did not verify TLS certificates presented by vCenter.
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 confidenceA man-in-the-middle vulnerability in Rubrik CDM 3.x and 4.x before 4.0.4-p2 allows attackers to intercept vCenter credentials because the system fails to validate TLS certificates presented by vCenter servers during connection establishment.
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<= 3.0.0>= 4.0.0, <= 4.0.4= 4.0.4CVSS 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
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
-
Check Rubrik CDM versionAccess the Rubrik administrative UI or use the CLI (rubrik-cli) to retrieve the installed CDM version. Compare it against the affected ranges: <= 3.0.0 or >= 4.0.0 through 4.0.4 (including 4.0.4).Affected if The installed version falls within <= 3.0.0 or 4.0.0 to 4.0.4.
-
Identify configured vCenter connectionsFrom the Rubrik UI, navigate to the vCenter inventory or connection settings page. Alternatively, query the Rubrik API endpoint for configured vCenter servers (e.g., GET /internal/v1/vmware/vcenter).Affected if One or more vCenter servers are registered and configured for backup or replication.
-
Verify TLS certificate validation behaviorAttempt a test connection from Rubrik to a vCenter server with an untrusted or mismatched TLS certificate. Observe whether the connection succeeds despite certificate validation failures, or check Rubrik logs for TLS handshake errors indicating missing validation.Affected if The connection succeeds when it should fail due to certificate mismatch, indicating certificate validation is not enforced.
You are affected if your Rubrik CDM version is 3.x through 3.0.0 or 4.0.0 through 4.0.4, and you have vCenter connections configured, with TLS certificate validation not properly enforced.
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 Rubrik CDM to version 4.0.4-p2 or later which implements proper TLS certificate verification for vCenter connections.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-5761 — 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-2018-5761 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