Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local access to Dell endpoint
-
ExploitExtract hard-coded cryptographic key from DCC
-
ExecutionDecrypt protected sensitive data
-
ImpactInformation disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
|
| Exploitation Conditions | Requires local access to a system with Dell Command | Configure installed at a version prior to 5.2.3.35; no authentication or user interaction is needed once local access exists (AV:L/PR:N/UI:N). Exploitation hinges on the attacker recovering the hard-coded cryptographic key embedded in the product and having access to data encrypted with it. The primary limiting factor is the mandatory local presence on the affected endpoint - remote network exploitation is not possible - which confines realistic risk to scenarios of insider access, prior foothold, or multi-user/shared Dell workstations. Impact is limited to confidentiality (information disclosure) with no integrity or availability effect. |
| Impact | This is a moderate-severity, local-access information disclosure flaw whose signals are internally consistent rather than conflicting. The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 6.2) establishes that exploitation requires local access to the system but no authentication or user interaction, with high confidentiality impact and no integrity or availability impact - matching the CWE-321 (hard-coded cryptographic key) root cause, where any party able to read the key or key-protected data locally can decrypt it. No EPSS score, CISA KEV listing, SSVC decision, or public POC was provided in the input, so there is no evidence of active or probable exploitation; this reads as a low-urgency patch-on-cycle item rather than an emergency. The AV:L requirement is the dominant limiting factor: an attacker must already have local presence on a Dell endpoint, which substantially narrows real-world risk despite the 'PR:N' (unauthenticated) metric. Note the common tension in hard-coded-key CVEs - the key is typically universal across all installs, so once extracted by one researcher it is effectively known everywhere, which can elevate practical risk beyond what the per-instance local vector implies; verify the nature of the protected data with Dell's advisory DSA-2026-378. |
| Exploit ScenarioDerived | An attacker with local access to a Dell endpoint running Dell Command | Configure below 5.2.3.35 locates the hard-coded cryptographic key embedded in the product and uses it to decrypt sensitive data (such as stored configuration secrets or credentials) protected by that key. No authentication or user interaction is required once local access is obtained. No public exploit was identified at time of analysis, though a hard-coded key is typically trivial to recover via static analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Local information disclosure in Dell Command | Configure (DCC) versions prior to 5.2.3.35 stems from a hard-coded cryptographic key embedded in the product, allowing an unauthenticated attacker with local access (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 6.2) to recover that key and decrypt data protected with it. There is no integrity or availability impact, and remote network exploitation is not possible - the attacker must already have a local presence on the endpoint, so realistic exposure is confined to insider scenarios, post-compromise footholds, or shared/multi-user Dell workstations. No public exploit code or confirmed active exploitation was identified in the available intelligence at time of analysis, and the primary limiting factor remains the mandatory local access requirement; Dell published advisory DSA-2026-378 covering this and other issues in the same release.
RemediationAI
Vendor-released patch: upgrade Dell Command | Configure to 5.2.3.35 or later - this is the version threshold defined by Dell Security Advisory DSA-2026-378 (https://www.dell.com/support/kbdoc/en-us/000502471/dsa-2026-378-security-update-for-dell-command-configure-for-multiple-vulnerabilities), which should be consulted for the complete list of fixes in that release and any Dell-provided deployment guidance. Because exploitation requires only local access and the key is static across installations, patching the binary alone does not retroactively protect data already encrypted or protected with the compromised hard-coded key: treat that key as burned and re-key or rotate any secrets, credential stores, configuration packages, or encrypted artifacts that were protected with DCC's embedded key, then re-issue them under the patched version. Until the upgrade is deployed, the most effective compensating control is to restrict local interactive logon on hosts running DCC to a small, trusted administrative group and to remove DCC from ordinary multi-user or shared workstations where non-privileged users have filesystem read access - the trade-off is reduced administrator convenience and potential disruption to configuration workflows on shared endpoints. Additional low-cost hardening includes tightening filesystem ACLs on the DCC installation directory so non-administrative users cannot read the application's key material, and monitoring for unexpected reads or copies of DCC files, though ACL restrictions only raise the bar and are not a substitute for the patch since an attacker with any elevated or SYSTEM-level local access can still recover the key. If DCC is not operationally required on a given endpoint, uninstalling it removes the exposure entirely at the cost of losing local BIOS configuration capability on that machine.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-321 (Use of Hard-coded Cryptographic Key): DCC ships with a static cryptographic key compiled into or packaged with the application rather than deriving or securely provisioning a per-installation secret. Because the key is identical across deployments and is recoverable from the local installation, any party with filesystem access on the host can extract it and then decrypt or forge artifacts that were protected with the same key - in this case resulting in confidentiality loss (C:H) with no integrity or availability effect (I:N/A:N). Dell Command | Configure is the client-side BIOS/system configuration utility in Dell's Command Suite, typically installed on managed Dell commercial endpoints and used by administrators to build and apply configuration packages; this deployment model means the tool and its key material are present on many ordinary user workstations, not just hardened admin Jump hosts, which broadens the pool of locally positioned potential attackers. The CVSS vector confirms the access profile: AV:L (local only), AC:L, PR:N (no authentication required once local access exists), UI:N (no user interaction), scope unchanged, so no privilege boundary crossing is required to trigger the disclosure - only local reachability of the key. NVD references the vendor advisory (Dell DSA-2026-378) as the authoritative source; no CPE strings, EPSS score, KEV entry, or public exploit reference were supplied with the available data, so the defect should be treated as a design/secret-management weakness rather than a remotely exploitable or actively weaponized remote-code-execution-style bug. Our independent assessment concurs with the vendor vector and finds the available signals internally consistent rather than conflicting.
Know when Command Configure gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Hard-coded key is readable with local access and no auth (AV:L/PR:N/AC:L), yielding high confidentiality disclosure with no integrity or availability impact.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
Dell Command | Configure (DCC), versions prior to 5.2.3.35 contain a Use of Hard-coded Cryptographic Key vulnerability. An unauthenticated attacker with local access could potentially exploit this vulnerability, leading to Information disclosure.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Command Configure
View allDell Command | Configure, versions prior to 4.11.0, contains an improper access control vulnerability. Rated high severi
Dell Command | Configure versions prior to 4.11.0, contain an improper access control vulnerability. Rated high severity
Dell Command Configure versions prior to 4.2.1 contain an uncontrolled search path vulnerability. Rated high severity (C
EUVD-2026-93663
GHSA-h4pq-pc4p-6v72
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB