dbcve.org
Cohesity DataplatformApplication · Cohesity

CVE-2023-33295

MEDIUM · 6.5 CVSS v3.1 Published 2024-01-19
Fix available
A fix is available. Upgrade to after 7.0.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Cohesity DataProtect prior to 6.8.1_u5 or 7.1 was discovered to have a incorrect access control vulnerability due to a lack of TLS Certificate Validation.

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 confidence

Cohesity DataProtect lacks TLS certificate validation in its network communications, allowing man-in-the-middle attackers to intercept or modify traffic. This incorrect access control vulnerability could enable unauthorized access to sensitive data during transit.

MitigationEnable and enforce TLS certificate validation across all network communications in Cohesity DataProtect, and upgrade to version 6.8.1_u5 or 7.1 or later.

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
Cohesity DataplatformApplication
Affected:<= 7.0.1

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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checks

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

  1. Identify Cohesity Dataplatform version
    Use the Cohesity management interface or CLI to retrieve the currently installed Dataplatform version number
    Affected if The installed version is 7.0.1 or any earlier version (7.0.1, 7.0.0, 6.x, etc.)
  2. Verify TLS certificate validation configuration
    Examine the network security settings within the Cohesity DataProtect configuration to determine whether TLS certificate validation is explicitly enabled or disabled for outbound and inbound communications
    Affected if TLS certificate validation is not explicitly enabled, is set to disabled, or is configured to allow invalid or self-signed certificates
  3. Inspect SSL/TLS protocol settings
    Review the SSL/TLS protocol configuration for data protection jobs and replication traffic to check if certificate verification is enforced
    Affected if Certificate verification is not enforced or is set to optional for any data protection network communications
  4. Check for custom certificate trust settings
    Look for any custom trust store or certificate validation bypass configurations in the DataProtect network settings
    Affected if Custom settings exist that skip certificate validation or accept all certificates

A user is affected if their Cohesity Dataplatform version is 7.0.1 or earlier AND TLS certificate validation is not explicitly enabled in their network communication settings.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 7.0.1
Interim mitigation

Enable and enforce TLS certificate validation across all network communications in Cohesity DataProtect, and upgrade to version 6.8.1_u5 or 7.1 or later.

Recommended fix High confidence

Upgrade to Cohesity 6.8.1_u5 (6.x branch) or 7.1 (7.x branch)

  1. 1. Identify the current Cohesity DataProtect version by checking the cluster management UI or using the 'cohesity cluster version' CLI command.
  2. 2. If currently running version 6.8.1 or earlier, upgrade to version 6.8.1_u5 (the patched update for the 6.x branch).
  3. 3. Alternatively, if planning to move to the 7.x branch, upgrade directly to version 7.1 which contains the fix.
  4. 4. Before upgrading, review Cohesity upgrade prerequisites and ensure adequate storage and resources are available.
  5. 5. Perform the upgrade through the Cohesity management interface or CLI using 'cohesity cluster upgrade' with the appropriate upgrade package.
  6. 6. After upgrade completes, verify the version number matches the expected fixed version (6.8.1_u5 or 7.1).
Caveat Review Cohesity release notes for any configuration or feature changes between versions; some UI paths or API endpoints may have changed in 7.x

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cohesity Dataplatform Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33295 — 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-2023-33295 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