CVE-2024-36782
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 · uneditedTOTOLINK CP300 V2.0.4-B20201102 was discovered to contain a hardcoded password vulnerability in /etc/shadow.sample, 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 · moderate confidenceThe TOTOLINK CP300 router firmware V2.0.4-B20201102 contains a hardcoded root password stored in /etc/shadow.sample. Attackers who obtain this password (which may be distributed with the firmware) can authenticate as root to the device, achieving full administrative control.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.4-b20201102CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the router model through the web admin interface, device label, or by accessing the device's system information page. Confirm it is a Totolink CP300 device.Affected if The device is not a Totolink CP300 router.
-
Check the installed firmware versionAccess the router's web admin interface and navigate to the firmware/version information page, or use the command line (if accessible) to query the firmware version.Affected if The firmware version is 2.0.4-b20201102.
-
Inspect /etc/shadow.sample for hardcoded root passwordIf you have firmware extraction tools or telnet/ssh access to the device, examine the file /etc/shadow.sample. Look for a root password hash entry that appears in the firmware image or file system.Affected if A root password entry exists in /etc/shadow.sample and the same password is distributed with the firmware.
-
Check if remote admin access is enabledIn the router's web admin interface, navigate to the remote management or WAN access settings. Determine if remote administration (web, telnet, or SSH) is enabled for WAN-facing interfaces.Affected if Remote administrative access is enabled and the device is internet-facing.
You are affected if you are running Totolink CP300 firmware version 2.0.4-b20201102 and the /etc/shadow.sample file with the hardcoded root password exists in your firmware or device.
Generated from the published advisory. Verify against your own configuration.
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 dataRemove the hardcoded password from /etc/shadow.sample and regenerate with a cryptographically secure password; apply any vendor firmware update if available; disable remote admin access via WAN until patched.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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