dbcve.org
DataplatformApplication · Cohesity

CVE-2019-11242

HIGH · 8.1 CVSS v3.0 Published 2019-07-12
Fix available
A fix is available. Upgrade to 6.1.1c or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
A man-in-the-middle vulnerability related to vCenter access was found in Cohesity DataPlatform version 5.x and 6.x prior to 6.1.1c. Cohesity clusters did not verify TLS certificates presented by vCenter. This vulnerability could expose Cohesity user credentials configured to access 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 confidence

Cohesity DataPlatform versions 5.x and 6.x prior to 6.1.1c fail to verify TLS certificates presented by vCenter during authentication, allowing man-in-the-middle attackers to intercept and steal configured vCenter user credentials.

MitigationUpgrade to Cohesity DataPlatform version 6.1.1c or later which implements proper TLS certificate validation for vCenter connections.

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
DataplatformApplication
Affected:>= 5.0, < 6.1.1c

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Cohesity DataPlatform version
    Access the Cohesity administrative interface or use the CLI command 'cohesity cluster version' to determine the installed DataPlatform version
    Affected if The installed version is 5.x or 6.x prior to 6.1.1c (e.g., 5.0 to 6.1.1b)
  2. Identify configured vCenter connections
    Navigate to the Cohesity UI under Sources > vCenter or use the API endpoint /clusters/protectionSources/virtualization to list configured vCenter connections
    Affected if Any vCenter source is configured and registered with the Cohesity DataPlatform cluster
  3. Verify vCenter authentication is in use
    Check the vCenter connection configuration to confirm that vCenter authentication (with stored credentials) is enabled rather than only using single sign-on
    Affected if The vCenter is configured with stored user credentials for authentication rather than SSO-only

You are affected if your Cohesity DataPlatform version is 5.0 through 6.1.1b AND you have at least one vCenter connection configured with stored credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 6.1.1c or later
Fixed in 6.1.1c
Interim mitigation

Upgrade to Cohesity DataPlatform version 6.1.1c or later which implements proper TLS certificate validation for vCenter connections.

Fix this in Dataplatform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11242 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11242 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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