Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues.
Metrics
Affected Vendors & Products
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Fri, 24 Oct 2025 23:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Deck Mate 2 lacks a verified secure-boot chain and runtime integrity validation for its controller and display modules. Without cryptographic boot verification, an attacker with physical access can modify or replace the bootloader, kernel, or filesystem and gain persistent code execution on reboot. This weakness allows long-term firmware tampering that survives power cycles. The vendor indicates that more recent firmware updates strengthen update-chain integrity and disable physical update ports to mitigate related attack avenues. | |
| Title | Shuffle Master Deck Mate 2 Missing Secure Boot | |
| Weaknesses | CWE-1326 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2025-10-24T23:04:11.948Z
Reserved: 2025-04-15T19:15:22.611Z
Link: CVE-2025-34502
No data.
Status : Received
Published: 2025-10-24T23:15:46.893
Modified: 2025-10-24T23:15:46.893
Link: CVE-2025-34502
No data.
OpenCVE Enrichment
No data.