{"id":72321,"date":"2025-10-25T02:45:46","date_gmt":"2025-10-24T23:15:46","guid":{"rendered":"https:\/\/afaghhosting.net\/blog\/cve-2025-34500-shuffle-master-deck-mate-2-insecure-update-chain\/"},"modified":"2025-10-25T02:45:46","modified_gmt":"2025-10-24T23:15:46","slug":"cve-2025-34500-shuffle-master-deck-mate-2-insecure-update-chain","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/cve-2025-34500-shuffle-master-deck-mate-2-insecure-update-chain\/","title":{"rendered":"CVE-2025-34500 &#8211; Shuffle Master Deck Mate 2 Insecure Update Chain"},"content":{"rendered":"<p>CVE ID : CVE-2025-34500<\/p>\n<p>Published :  Oct. 24, 2025, 11:15 p.m. | 1\u00a0hour, 28\u00a0minutes ago<\/p>\n<p>Description : Deck Mate 2&#8217;s firmware update mechanism accepts packages without cryptographic signature verification, encrypts them with a single hard-coded AES key shared across devices, and uses a truncated HMAC for integrity validation. Attackers with access to the update interface &#8211; typically via the unit&#8217;s USB update port &#8211; can craft or modify firmware packages to execute arbitrary code as root, allowing persistent compromise of the device&#8217;s integrity and deck randomization process. Physical or on-premises access remains the most likely attack path, though network-exposed or telemetry-enabled deployments could theoretically allow remote exploitation if misconfigured. The vendor confirmed that firmware updates have been issued to correct these update-chain weaknesses and that USB update access has been disabled on affected units.<\/p>\n<p>Severity: 7.0 | HIGH<\/p>\n<p>Visit the link for more details, such as CVSS details, affected products, timeline, and more&#8230;\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>CVE ID : CVE-2025-34500 Published : Oct. 24, 2025, 11:15 p.m. | 1\u00a0hour, 28\u00a0minutes ago Description : Deck Mate 2&#8217;s firmware update mechanism accepts packages without cryptographic signature verification, encrypts them with a single hard-coded AES key shared across devices, and uses a truncated HMAC for integrity validation. Attackers with access to the update interface &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-72321","post","type-post","status-publish","format-standard","hentry","category-vulnerability"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/72321","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=72321"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/72321\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=72321"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=72321"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=72321"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}