CVE-2021-28124
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 in Cohesity DataPlatform support channel in version 6.3 up to 6.3.1g, 6.4 up to 6.4.1c and 6.5.1 through 6.5.1b. Missing server authentication in impacted versions can allow an attacker to Man-in-the-middle (MITM) support channel UI session to Cohesity DataPlatform cluster.
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 confidenceCohesity DataPlatform versions 6.3 through 6.3.1g, 6.4 through 6.4.1c, and 6.5.1 through 6.5.1b contain a missing server authentication vulnerability in the support channel UI. An attacker positioned on the network between the client and the Cohesity cluster could intercept or manipulate the support channel session due to the lack of proper server certificate validation, enabling man-in-the-middle attacks.
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>= 6.3, <= 6.3.1g>= 6.4, <= 6.4.1c>= 6.5.1, <= 6.5.1bCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Cohesity DataPlatform versionUse the Cohesity management interface or CLI to retrieve the installed DataPlatform version. This is typically found in the cluster settings or via command: `cohesity cluster version` or through the web UI dashboard.Affected if The installed version falls within 6.3 to 6.3.1g, 6.4 to 6.4.1c, or 6.5.1 to 6.5.1b.
-
Identify if support channel UI is in useLocate the support channel or support portal feature within the Cohesity DataPlatform web interface. This is typically accessed through the Help or Support sections of the UI.Affected if The support channel UI feature is accessible or has been used on the cluster.
-
Check TLS certificate validation settingsExamine the configuration for the support channel connection. Look for TLS/SSL settings that control server certificate validation. The exact location varies by deployment but is generally found in the support channel or remote support settings.Affected if Server certificate validation is disabled, set to optional, or not properly configured for the support channel connection.
-
Verify network exposureAssess whether the Cohesity cluster support channel is accessible over the network. Determine if the support channel communicates with external servers and whether traffic traverses untrusted networks.Affected if The support channel traffic can be intercepted by an attacker positioned between the client and the Cohesity cluster.
The environment is affected if the installed Cohesity DataPlatform version falls within the affected ranges AND the support channel UI feature is enabled or accessible without proper server certificate validation.
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 dataImplement proper TLS server authentication and certificate validation in the support channel. Ensure the support channel verifies the server's identity before establishing the connection.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28124 — 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-2021-28124 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