{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-34500 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34500 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34500 is a high-severity vulnerability in Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 2, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-34500 and fix it if it is affected.\n\nWhat it is: CVE-2025-34500 is a high-severity vulnerability in Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 2, published on 24 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-34500 in the wild and no public exploit code.\n\nAffected product: Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-34500/ (Markdown: https://insights.sbomify.com/CVE-2025-34500/index.md)","id":"CVE-2025-34500","markdown":"https://insights.sbomify.com/CVE-2025-34500/index.md","name":"CVE-2025-34500","record":{"aliases":["GHSA-rhx6-vj26-2frq"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Card shuffling machine","requires_auth":"none","summary":"Attackers with physical access can exploit hardcoded keys and missing signature checks in the update mechanism to execute arbitrary code as root.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-321","name":"Use of Hard-coded Cryptographic Key"}],"description":"Deck Mate 2'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 - typically via the unit's USB update port - can craft or modify firmware packages to execute arbitrary code as root, allowing persistent compromise of the device'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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Shuffle Master Deck Mate 2 Insecure Update Chain","id":"CVE-2025-34500","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Shuffle Master Deck Mate 2 Hard-coded Credentials \u0026 Exposed Services","id":"CVE-2025-34501"},"packages":[],"prev":{"headline":"AnyDesk 9.0.1 Unquoted Service Path Privilege Escalation Vulnerability","id":"CVE-2025-34499"},"products":["Deck Mate 2"],"published":"2025-10-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc."]},"summary":"Attackers with physical access can exploit hardcoded keys and missing signature checks in the update mechanism to execute arbitrary code as root.","url":"https://insights.sbomify.com/CVE-2025-34500/"}