dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2021-47796

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-16
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
Public exploit 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
Denver SHC-150 Smart Wifi Camera contains a hardcoded telnet credential vulnerability that allows unauthenticated attackers to access a Linux shell. Attackers can connect to port 23 using the default credential to execute arbitrary commands on the camera's operating system.

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 Denver SHC-150 Smart Wifi Camera contains a hardcoded telnet credential vulnerability. Unauthenticated attackers can connect to port 23 using the default credential to gain a Linux shell and execute arbitrary commands on the device's operating system.

MitigationContact Denver for firmware updates to remove the hardcoded credential; if unavailable, disable telnet access on the device, implement network segmentation to restrict access, or replace the device with a secure alternative.

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. Identify device model
    Access the device web interface or check the device label/metadata to confirm the exact model is Denver SHC-150 Smart Wifi Camera
    Affected if The device is a Denver SHC-150 Smart Wifi Camera
  2. Scan for telnet port accessibility
    Perform a network port scan targeting the device IP on TCP port 23 to determine if port 23 is open and reachable
    Affected if Port 23/telnet is open and accessible from an attacker-controlled network location
  3. Verify telnet service responds
    Establish a telnet connection to the device IP on port 23 and observe if a login prompt appears
    Affected if The telnet service accepts connections and presents a login prompt
  4. Test hardcoded credential authentication
    Attempt to log in via telnet using the known hardcoded default credential for this device
    Affected if The default hardcoded credential successfully authenticates and provides shell access

The environment is affected if the device is a Denver SHC-150 Smart Wifi Camera with telnet port 23 open and accessible, where the hardcoded default credential grants unauthenticated 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

Contact Denver for firmware updates to remove the hardcoded credential; if unavailable, disable telnet access on the device, implement network segmentation to restrict access, or replace the device with a secure alternative.

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-2021-47796 — 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-2021-47796 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