dbcve.org
Gnc Cw013 FirmwareOperating system · Mygeeni

CVE-2020-29000

HIGH · 7.2 CVSS v3.1 Published 2021-01-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An issue was discovered on Geeni GNC-CW013 doorbell 1.8.1 devices. A vulnerability exists in the RTSP service that allows a remote attacker to take full control of the device with a high-privileged account. By sending a crafted message, an attacker is able to remotely deliver a telnet session. Any attacker that has the ability to control DNS can exploit this vulnerability to remotely login to the device and gain access to the camera 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 · moderate confidence

The Geeni GNC-CW013 doorbell firmware 1.8.1 contains a vulnerability in its RTSP (Real Time Streaming Protocol) service. An attacker who can control DNS resolution for the device can send specially crafted RTSP messages that trigger the device to initiate an outbound telnet session back to the attacker, granting high-privileged remote access to the camera system.

MitigationPrimary remediation is to obtain and apply any vendor firmware update. As a compensating control, implement strict network segmentation to isolate the doorbell from untrusted networks and secure DNS infrastructure to prevent DNS hijacking that would enable exploitation.

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
Gnc Cw013 FirmwareOperating system
Affected:= 1.8.1

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

CVSS:3.1/AV:N/AC:L/PR:H/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 the firmware version of the Geeni GNC-CW013 doorbell
    Access the device admin interface or check the device settings to locate the firmware version information. This is typically found under Device Info, About, or Settings > Device Settings. Compare the displayed version to 1.8.1.
    Affected if The firmware version is exactly 1.8.1
  2. Verify if the RTSP service is enabled on the device
    Log into the device web interface or mobile app and navigate to the network or advanced settings. Look for an RTSP or streaming service setting and confirm whether it is turned on.
    Affected if RTSP streaming is enabled and accessible on the device
  3. Inspect the DNS server configuration on the device
    Check the device network settings to see which DNS servers are configured. This is usually found under Network Settings, WiFi Settings, or DHCP configuration. Verify that the DNS servers point to trusted and controlled servers.
    Affected if The device is configured to use DNS servers that are not under the owner's control, or DNS settings are set to automatic with risk of hijacking
  4. Check for unexpected outbound network connections
    Use network monitoring tools or check the router/firewall logs for any outbound telnet connections (port 23) originating from the doorbell device IP address to external IP addresses.
    Affected if There are outbound telnet connections initiated by the device to unknown external IP addresses

A user is affected if their Geeni GNC-CW013 doorbell runs firmware version 1.8.1, has RTSP service enabled, and operates in an environment where DNS resolution can be controlled by an attacker.

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

Primary remediation is to obtain and apply any vendor firmware update. As a compensating control, implement strict network segmentation to isolate the doorbell from untrusted networks and secure DNS infrastructure to prevent DNS hijacking that would enable exploitation.

Fix this in Gnc Cw013 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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