dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2025-34501

HIGH · 7.0 CVSS v4.0 Published 2025-11-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Deck Mate 2 ships with static, hard-coded credentials for both the root shell and web UI. Multiple management services (SSH, HTTP, Telnet, SMB, X11) are enabled by default, and attackers with physical access to USB or Ethernet ports can use these default credentials to achieve administrative login and full system control.

MitigationImmediately change all default credentials, disable unused management services, restrict physical access to device ports, and update to the latest firmware build where USB access has been disabled.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Deck Mate 2 hardware in your environment
    Locate the physical device or check system inventory/asset documentation for Deck Mate 2 units
    Affected if The device is a Deck Mate 2 model
  2. Check if management services are enabled
    Access the device admin interface or run commands to list active network services (SSH port 22, HTTP port 80/443, Telnet port 23, SMB port 445, X11 port 6000)
    Affected if Any of SSH, HTTP, Telnet, SMB, or X11 services are running and accessible
  3. Verify credential status
    Log into the device admin panel or check configuration files to determine whether default credentials have been changed from factory settings
    Affected if Default credentials (root shell and web UI) have not been changed since initial setup
  4. Check for unused management interfaces
    Review the device network configuration to see which management protocols are permitted (Ethernet ports, USB debug interfaces)
    Affected if Multiple management services remain enabled when they are not needed for operations
  5. Inspect physical port access
    Examine physical security controls around USB, Ethernet, and serial ports on the device
    Affected if USB or Ethernet ports are accessible without restriction or monitoring
  6. Confirm firmware version
    Check the installed firmware version through device settings or boot logs against any manufacturer release notes
    Affected if Firmware is older than the latest build with USB access controls

You are affected if you operate a Deck Mate 2 device with default credentials still in place and management services enabled, allowing potential administrative access via accessible ports.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change all default credentials, disable unused management services, restrict physical access to device ports, and update to the latest firmware build where USB access has been disabled.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34501 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34501 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data