dbcve.org
CloudlinkApplication · Dell

CVE-2023-28076

HIGH · 7.5 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 7.1.3 or later.
See remediation →
84/100
Remediation priority · High
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
CloudLink 7.1.2 and all prior versions contain a broken or risky cryptographic algorithm vulnerability. An unauthenticated remote attacker could potentially exploit this vulnerability leading to some information disclosure.

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

CloudLink versions 7.1.2 and prior contain a broken or risky cryptographic algorithm vulnerability. An unauthenticated remote attacker could exploit weak or outdated cryptographic primitives (such as weak hashing, insecure cipher suites, or deprecated protocols) to decrypt sensitive communications or data, leading to information disclosure.

MitigationUpgrade to the latest CloudLink version that implements strong cryptographic algorithms (AES-256, SHA-256+, TLS 1.2+) and conduct a cryptographic code review to identify and replace any remaining weak or deprecated crypto implementations.

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
CloudlinkApplication
Affected:< 7.1.3

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

CVSS:3.1/AV:N/AC:L/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 checks

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

  1. Identify installed CloudLink version
    Locate and retrieve the current version of Dell CloudLink installed in your environment. This is typically found in the product's about page, installation directory, or via command-line version query.
    Affected if The installed version is 7.1.2 or any version prior to 7.1.3, indicating the product uses weak or outdated cryptographic primitives.
  2. Examine cryptographic configuration settings
    Review CloudLink's cryptographic configuration files or settings panel. Look for sections that define encryption algorithms, cipher suites, hashing methods, or protocol versions.
    Affected if Weak, deprecated, or non-compliant cryptographic algorithms are configured or enabled (such as MD5, SHA-1, TLS 1.0/1.1, or weak AES variants).
  3. Identify cipher suites in use
    If CloudLink exposes SSL/TLS endpoints, inspect the enabled cipher suites. Use network scanning tools or review configuration to list active cipher suites.
    Affected if Insecure or weak cipher suites (such as those using 3DES, RC4, or export-grade ciphers) are enabled or negotiated.
  4. Verify protocol versions
    Check which TLS/SSL protocol versions are supported or enabled for communications between CloudLink components or clients.
    Affected if Deprecated protocols like TLS 1.0 or TLS 1.1 are still enabled or accepted.
  5. Inspect hashing implementations
    Review any custom code, scripts, or configuration that handles data hashing or password storage within the CloudLink deployment.
    Affected if Weak hashing algorithms (such as MD5 or SHA-1 without salting) are used for sensitive operations like password storage or data integrity.

Your environment is affected if the installed CloudLink version is prior to 7.1.3 or if weak cryptographic algorithms, deprecated protocols, or insecure cipher suites are currently in use.

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 7.1.3 or later
Fixed in 7.1.3
Interim mitigation

Upgrade to the latest CloudLink version that implements strong cryptographic algorithms (AES-256, SHA-256+, TLS 1.2+) and conduct a cryptographic code review to identify and replace any remaining weak or deprecated crypto implementations.

Recommended fix Moderate confidence

7.1.3

  1. Verify current CloudLink version is below 7.1.3 using the Dell support portal or product management interface
  2. Obtain CloudLink 7.1.3 or later from Dell's official support website (support.dell.com)
  3. Review Dell's upgrade documentation for CloudLink before proceeding
  4. Perform the upgrade following Dell's documented upgrade procedure
  5. Verify the upgrade was successful and the version is now 7.1.3 or later
  6. Confirm the cryptographic vulnerability is resolved

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

Fix this in Cloudlink Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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