Emc Data Domain OsOperating system · Dell

CVE-2023-23692

HIGH · 8.8 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 6.2.1.90 / 7.7.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Dell EMC prior to version DDOS 7.9 contain(s) an OS command injection Vulnerability. An authenticated non admin attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the application's underlying OS, with the privileges of the vulnerable application.

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

OS command injection vulnerability in Dell EMC DDOS product versions prior to 7.9. An authenticated non-admin user can inject and execute arbitrary OS commands on the underlying system with the application's privileges.

MitigationUpgrade Dell EMC DDOS to version 7.9 or later to remediate this vulnerability.

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
Emc Data Domain OsOperating system
Affected:< 6.2.1.90>= 7.0.0.0, < 7.9.0.0>= 7.7.1, < 7.7.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Data Domain OS version
    Run command 'show version' or 'system show version' on the Data Domain system to retrieve the installed OS version.
    Affected if Version is < 6.2.1.90, or >= 7.0.0.0 and < 7.9.0.0, or >= 7.7.1 and < 7.7.3
  2. Confirm non-admin user access is enabled
    Check user configuration via 'user list' or review authentication settings to determine if non-admin user accounts exist and can authenticate to the system.
    Affected if Non-admin user accounts are present and can authenticate (this is required for the vulnerability to be exploitable)
  3. Verify the management interface is accessible
    Confirm that the Data Domain management interface (GUI or CLI) is exposed and reachable for authenticated sessions.
    Affected if Management interface is accessible from network locations where non-admin users can connect

The environment is affected if the installed Data Domain OS version falls within any of the affected ranges AND non-admin user authentication is enabled on the system.

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 6.2.1.90 / 7.7.3 / 7.9.0.0 or later
Fixed in 6.2.1.907.7.37.9.0.0
Interim mitigation

Upgrade Dell EMC DDOS to version 7.9 or later to remediate this vulnerability.

Recommended fix High confidence

DDOS 7.9.0.0 or later (for 7.x branch); DDOS 6.2.1.90 or later (for 6.2.x branch)

  1. 1. Back up current Data Domain system configuration and data
  2. 2. Schedule maintenance window for upgrade (system will be temporarily unavailable)
  3. 3. Download Dell EMC Data Domain OS version 7.9.0.0 or later from Dell support portal
  4. 4. Upload the DDOS upgrade package to the Data Domain system
  5. 5. Follow Dell's standard upgrade procedure: run 'sysadmin upgrade' command or use Data Domain Enterprise Manager to initiate the upgrade
  6. 6. Verify the upgrade completed successfully by checking the DDOS version (run 'ddos -version' or 'system show version')
  7. 7. Confirm the upgrade completed without errors and the system is operational
Caveat Standard Data Domain OS upgrade may cause brief service interruption; review Dell upgrade guide for pre-upgrade checklist and compatibility requirements

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

Fix this in Emc Data Domain Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-23692 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