CVE-2025-36573VulnerabilityPublished 12 Jun 2025

CVE-2025-36573: Dell Smart Dock · Sensitive Data in Logs

Affects Dell Smart DockSource CVE Database V5

Not known to be exploited · CVSS 7.1 High : upgrade to 1.0.8.1 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.0.8.1

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Dell Smart Dock to 1.0.8.1.

Affected software

Product	Affected	Fixed in
Dell Smart Dock	Affected <1.0.8.1	Fixed in 1.0.8.1

AI-suggested

Implement strict physical security controls to limit local access to Dell Smart Dock devices, including secure office environments and access logging.

Monitor and audit local user activities on systems connected to Dell Smart Docks to detect unauthorized access attempts.

Until an official firmware patch is released by Dell, consider disabling or limiting the use of Smart Docks in sensitive environments or replacing them with alternative docking solutions that do not exhibit this vulnerability.

Use endpoint security solutions capable of detecting unusual access to log files or attempts to extract sensitive data from local storage.

Educate users about the risks of leaving devices unattended and the importance of reporting lost or stolen hardware promptly.

Once Dell releases a firmware update addressing this vulnerability, prioritize its deployment across all affected devices in the organization.

Review and restrict logging configurations where possible to minimize sensitive data being written to logs, if configurable.

Implement network segmentation to limit the potential impact of compromised credentials obtained via this vulnerability.

Description

Dell Smart Dock Firmware, versions prior to 01.00.08.01, contain an Insertion of Sensitive Information into Log File vulnerability. A user with local access could potentially exploit this vulnerability, leading to Information disclosure.

Impact

For European organizations, the impact of CVE-2025-36573 can be significant, especially in sectors where Dell Smart Docks are widely deployed, such as corporate offices, government agencies, and critical infrastructure. The exposure of sensitive information through log files can lead to unauthorized disclosure of credentials or cryptographic material, which in turn could enable lateral movement within networks, privilege escalation, or compromise of connected systems. Since the vulnerability requires local access, the threat is heightened in environments with shared workspaces, hot-desking, or where physical security controls are lax. Confidentiality breaches could undermine compliance with GDPR and other data protection regulations, leading to legal and reputational consequences. Additionally, the vulnerability could be exploited by malicious insiders or attackers who gain temporary local access, making it a concern for organizations with high-value intellectual property or sensitive operational data. The lack of impact on integrity and availability reduces the risk of direct system disruption, but the confidentiality breach alone is critical enough to warrant immediate attention.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

dell.com/support/kbdoc/en-us/000323183/dsa-2025-218 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 15:54 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats