{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-34501 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-34501 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-34501 is a high-severity vulnerability in Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 2, published on 3 Nov 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-34501 and fix it if it is affected.\n\nWhat it is: CVE-2025-34501 is a high-severity vulnerability in Light \u0026 Wonder, Inc. / SHFL Entertainment, Inc. / Shuffle Master, Inc. Deck Mate 2, published on 3 Nov 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-34501 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-34501/ (Markdown: https://insights.sbomify.com/CVE-2025-34501/index.md)","id":"CVE-2025-34501","markdown":"https://insights.sbomify.com/CVE-2025-34501/index.md","name":"CVE-2025-34501","record":{"aliases":["GHSA-434j-26h4-7637"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"casino card shuffler","requires_auth":"none","summary":"Hard-coded credentials and exposed services allow attackers with local access to gain administrative control and modify firmware on Deck Mate 2 shufflers.","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-798","name":"Use of Hard-coded Credentials"}],"description":"Deck Mate 2 is distributed with static, hard-coded credentials for the root shell and web user interface, while multiple management services (SSH, HTTP, Telnet, SMB, X11) are enabled by default. If an attacker can reach these interfaces - most often through local or near-local access such as connecting to the USB or Ethernet ports beneath the table - the built-in credentials permit administrative login and full control of the system. Once authenticated, an attacker can access firmware utilities, modify controller software, and establish persistent compromise. Remote attack paths via network, cellular, or telemetry links may exist in specific configurations but generally require additional capabilities or operator error. The vendor reports that USB access has been disabled in current firmware builds.","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 Hard-coded Credentials \u0026 Exposed Services","id":"CVE-2025-34501","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Shuffle Master Deck Mate 2 Missing Secure Boot","id":"CVE-2025-34502"},"packages":[],"prev":{"headline":"Shuffle Master Deck Mate 2 Insecure Update Chain","id":"CVE-2025-34500"},"products":["Deck Mate 2"],"published":"2025-11-03","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":"Hard-coded credentials and exposed services allow attackers with local access to gain administrative control and modify firmware on Deck Mate 2 shufflers.","url":"https://insights.sbomify.com/CVE-2025-34501/"}