dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2024-54751

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
COMFAST CF-WR630AX v2.7.0.2 was discovered to contain a hardcoded password vulnerability in /etc/shadow, which allows attackers to log in as root.

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

The COMFAST CF-WR630AX router firmware v2.7.0.2 contains a hardcoded password stored in /etc/shadow, enabling unauthenticated attackers to gain root shell access by authenticating with this credential.

MitigationImmediately change the default root password through the admin interface and apply any vendor firmware updates. If no patch is available, replace the device or implement strict network isolation to prevent external access.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm device model is COMFAST CF-WR630AX
    Access the router admin interface or check the device label to verify the exact model number
    Affected if Device is not a COMFAST CF-WR630AX router
  2. Check firmware version is v2.7.0.2
    Log into the router admin interface and navigate to System Settings or Status page to view the firmware version, or use the command line if accessible
    Affected if Firmware version is not v2.7.0.2
  3. Inspect /etc/shadow for hardcoded password hash
    Access the router filesystem via SSH, telnet, or by extracting the firmware binary and examine the /etc/shadow file for a hardcoded root password hash
    Affected if A hardcoded password hash exists in /etc/shadow that was not set by the administrator
  4. Verify root shell access with hardcoded credential
    Attempt SSH or telnet login to the router using the hardcoded credential discovered in /etc/shadow
    Affected if Authentication succeeds with the hardcoded credential and provides root shell access

Device is affected if it is a COMFAST CF-WR630AX running firmware v2.7.0.2 with a hardcoded password present in /etc/shadow that grants root shell access.

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 the default root password through the admin interface and apply any vendor firmware updates. If no patch is available, replace the device or implement strict network isolation to prevent external access.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54751 — 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-2024-54751 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