{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-34503 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34503 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34503 is a high-severity code injection vulnerability in Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 1, 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-34503 and fix it if it is affected.\n\nWhat it is: CVE-2025-34503 is a high-severity code injection vulnerability in Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 1, 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-34503 in the wild and no public exploit code.\n\nAffected product: Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 1. 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-34503/ (Markdown: https://insights.sbomify.com/CVE-2025-34503/index.md)","id":"CVE-2025-34503","markdown":"https://insights.sbomify.com/CVE-2025-34503/index.md","name":"CVE-2025-34503","record":{"aliases":["GHSA-4v5m-7xcr-cg68"],"analysis":{"component_type":"hardware_firmware","fix_type":"end_of_life","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 replace EEPROM firmware to execute arbitrary code on Deck Mate 1 shufflers, which lack secure boot and are end-of-life.","user_interaction":"not_required","vuln_class":"code_injection"},"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-1326","name":"Missing Immutable Root of Trust in Hardware"}],"description":"Deck Mate 1 executes firmware directly from an external EEPROM without verifying authenticity or integrity. An attacker with physical access can replace or reflash the EEPROM to run arbitrary code that persists across reboots. Because this design predates modern secure-boot or signed-update mechanisms, affected systems should be physically protected or retired from service. The vendor has not indicated that firmware updates are available for this legacy model.","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 1 Unauthenticated EEPROM Firmware Execution","id":"CVE-2025-34503","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"KodExplorer 4.52 Open Redirect Vulnerability via User Login Endpoint","id":"CVE-2025-34504"},"packages":[],"prev":{"headline":"Shuffle Master Deck Mate 2 Missing Secure Boot","id":"CVE-2025-34502"},"products":["Deck Mate 1"],"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 replace EEPROM firmware to execute arbitrary code on Deck Mate 1 shufflers, which lack secure boot and are end-of-life.","url":"https://insights.sbomify.com/CVE-2025-34503/"}