Malicious payload execution via improper signature verification
Published Feb 1, 2023 · Updated Mar 27, 2025
Improper signature verification in Dell Command | Update before 4.7 allows local users to execute malicious payloads through the update workflow. The proprietary Get Applicable Driver component accepts a driver payload without properly validating its cryptographic signature; Dell has not published the exact validation error. Exploitation requires a low-privileged local user and can execute attacker-controlled code with confidentiality, integrity, and availability impact.
Summary
What happened
Improper signature verification in Dell Command | Update before 4.7 allows local users to execute malicious payloads through the update workflow. The proprietary Get Applicable Driver component accepts a driver payload without properly validating its cryptographic signature; Dell has not published the exact validation error. Exploitation requires a low-privileged local user and can execute attacker-controlled code with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2022-34459
- Published
- Feb 1, 2023
- Updated
- Mar 27, 2025
- Vendor
- Dell
- Product
- Dell Command | Update
- Classifications
- CWE-347
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 1, 2023CVE publishedPublication date reported by the CVE source.
- Mar 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <4.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo