{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-34502 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34502 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34502 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-34502 and fix it if it is affected.\n\nWhat it is: CVE-2025-34502 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-34502 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-34502/ (Markdown: https://insights.sbomify.com/CVE-2025-34502/index.md)","id":"CVE-2025-34502","markdown":"https://insights.sbomify.com/CVE-2025-34502/index.md","name":"CVE-2025-34502","record":{"aliases":["GHSA-3xvc-wfvf-2p2f"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gaming table controller","requires_auth":"none","summary":"Attackers with physical access can bypass secure boot to install persistent malicious firmware on Deck Mate 2 gaming controllers.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"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-1326","name":"Missing Immutable Root of Trust in Hardware"}],"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.","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 Missing Secure Boot","id":"CVE-2025-34502","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Shuffle Master Deck Mate 1 Unauthenticated EEPROM Firmware Execution","id":"CVE-2025-34503"},"packages":[],"prev":{"headline":"Shuffle Master Deck Mate 2 Hard-coded Credentials \u0026 Exposed Services","id":"CVE-2025-34501"},"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":"total"},"state":"PUBLISHED","updated":"2026-07-28","vendors":["Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc."]},"summary":"Attackers with physical access can bypass secure boot to install persistent malicious firmware on Deck Mate 2 gaming controllers.","url":"https://insights.sbomify.com/CVE-2025-34502/"}