Security readout for executives and security teams
Plain-English summary
Deck Mate 2 card shufflers contain built-in administrative credentials and expose several management services by default. Anyone who can physically or locally connect to an accessible interface may gain complete device control, alter controller software, or maintain persistent access. Broader remote exposure depends on site-specific connectivity and configuration.
Executive priority
Prioritize affected devices in publicly accessible or weakly supervised areas. Treat reachable management interfaces as a high-impact integrity risk because compromise could undermine device trust and operations. Immediately strengthen physical and network controls, inventory firmware, and obtain written vendor remediation guidance; evidence supplied does not justify claiming an Internet-wide emergency.
Technical view
CVE-2025-34501 is a CWE-798 hard-coded credential weakness affecting Deck Mate 2 version 0 as reported. Root-shell and web-interface credentials are static, while SSH, HTTP, Telnet, SMB, and X11 are enabled by default. CVSS 4.0 scores it 7.0, with physical attack proximity and high confidentiality, integrity, and availability impact.
Likely exposure
Highest exposure exists where attackers, contractors, patrons, or unauthorized staff can reach USB or Ethernet ports beneath gaming tables. Network, cellular, or telemetry paths may increase exposure in particular deployments, but the available evidence does not establish universal remote reachability. The affected-version designation and default status remain insufficiently detailed.
Exploitation context
The sources describe authenticated administrative compromise using embedded credentials, including firmware and controller modification. The CVE is not identified as CISA KEV in the supplied bundle, and no cited evidence establishes active exploitation in the wild. Most plausible access is physical or near-local; remote scenarios require additional connectivity, capability, or operator error.
Researcher notes
The record identifies version 0 but provides no CPEs, complete version range, credential-rotation mechanism, or definitive patch identifier. Current firmware reportedly disables USB, although other exposed services and credential behavior require vendor confirmation. Assessment should distinguish physical-port accessibility from routed network exposure and avoid interpreting the advisory alone as evidence of real-world exploitation.
Mitigation direction
- Contact Light & Wonder for current firmware and product-specific remediation guidance.
- Deploy current firmware builds reported to disable USB access, subject to vendor confirmation.
- Physically restrict access to beneath-table USB and Ethernet interfaces.
- Isolate devices from untrusted networks and tightly restrict management-service reachability.
- Disable unnecessary management services where supported by documented vendor procedures.
Validation and detection
- Inventory every Deck Mate 2 device, firmware build, location, and connected interface.
- Confirm with the vendor whether each installed build contains the reported remediation.
- Verify USB access is disabled on current firmware without attempting credential use.
- Review network controls for exposure of SSH, HTTP, Telnet, SMB, and X11.
- Examine authorized logs and integrity records for unexplained administrative or firmware changes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-798: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-34501 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
7HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ioactive.com/wp-content/uploads/2025/05/IOActive-card-shuffler-security.pdfCVE reference, VulnCheck · technical-description, exploit
- https://www.vulncheck.com/advisories/shuffle-master-deck-mate-2-hard-coded-credentials-and-exposed-servicesCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Credentials
Use of Hard-coded Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.