dbcve.org
Vxrail ManagerApplication · Dell

CVE-2022-46756

MEDIUM · 6.7 CVSS v3.1 Published 2023-02-01
Fix available
A fix is available. Upgrade to 7.0.410 or later.
See remediation →
69/100
Remediation priority · Elevated
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 VxRail, versions prior to 7.0.410, contain a Container Escape Vulnerability. A local high-privileged attacker could potentially exploit this vulnerability, leading to the execution of arbitrary OS commands on the container's underlying OS. Exploitation may lead to a system take over by an attacker.

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

Dell VxRail contains a container escape vulnerability in versions prior to 7.0.410. A local high-privileged attacker can exploit this vulnerability to escape the container isolation and execute arbitrary OS commands on the container's underlying host OS, potentially achieving full system takeover.

MitigationUpgrade Dell VxRail to version 7.0.410 or later to remediate this container escape 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
Vxrail ManagerApplication
Affected:< 7.0.410

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

CVSS:3.1/AV:L/AC:L/PR:H/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 if the system is Dell VxRail Manager
    Locate the VxRail Manager version information in the system management interface or by querying the VxRail Appliance API/CLI tools provided by Dell
    Affected if The system is running Dell VxRail Manager
  2. Determine the installed VxRail Manager version
    Query the VxRail Manager version through the management API, CLI, or system information panel. Compare the version number to 7.0.410
    Affected if The installed version is lower than 7.0.410 (for example, 7.0.400, 7.0.350, etc.)
  3. Verify if containerized workloads are running on VxRail
    Check the VxRail environment for any container-based workloads or Kubernetes/Kubernetes-related components that utilize container isolation
    Affected if Container isolation is in use and the VxRail version is below 7.0.410
  4. Review container runtime configuration and isolation boundaries
    Inspect the container runtime settings and verify that container-to-host isolation controls are properly enforced. Look for any signs of container escape attempts in system logs
    Affected if Container isolation exists and the version is vulnerable

The environment is affected if Dell VxRail Manager is installed with a version lower than 7.0.410 and containers are running on the system, allowing a high-privileged local attacker to escape container isolation and execute commands on the host OS.

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.0.410 or later
Fixed in 7.0.410
Interim mitigation

Upgrade Dell VxRail to version 7.0.410 or later to remediate this container escape vulnerability.

Recommended fix High confidence

7.0.410

  1. Log in to the VxRail Manager administrative interface or access via SSH with administrator credentials
  2. Verify current VxRail Manager version is below 7.0.410 by checking System > About or running 'vxrailadm --version'
  3. Download the VxRail Manager 7.0.410 (or later) update bundle from the Dell Support website (support.dell.com)
  4. Create a backup of current VxRail Manager configuration and ensure adequate snapshots are taken
  5. Initiate the upgrade through VxRail Manager UI: Navigate to Settings > Maintenance > Updates, or use command line: 'vxrailadm --update --bundle <path-to-bundle>'
  6. Monitor the upgrade progress and verify completion without errors
  7. After upgrade, confirm the new version is 7.0.410 or later using 'vxrailadm --version'
  8. Verify that VxRail cluster functionality is normal post-upgrade
Caveat Review Dell VxRail 7.0.410 release notes for any configuration or compatibility changes before upgrading

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

Fix this in Vxrail Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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