CVE-2020-28999
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 · uneditedAn issue was discovered in Apexis Streaming Video Web Application on Geeni GNC-CW013 doorbell 1.8.1 devices. A remote attacker can take full control of the camera with a high-privileged account. The vulnerability exists because a static username and password are compiled into a shared library (libhipcam.so) used to provide the streaming camera service.
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 confidenceA hardcoded credential vulnerability exists in the Apexis streaming video web application on Geeni GNC-CW013 doorbell firmware 1.8.1. Static username and password credentials are compiled directly into the libhipcam.so shared library that provides the camera streaming service. A remote attacker with high-privileged account access can exploit these hardcoded credentials to gain full administrative control over the camera device.
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= 1.8.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck if the device is a Geeni GNC-CW013 doorbell by reviewing the device label, web interface, or administrative consoleAffected if The device is not a Geeni GNC-CW013 doorbell, then it is not affected by this specific CVE
-
Check the firmware versionAccess the device administrative interface or use the vendor-provided app to view the firmware version informationAffected if Firmware version is exactly 1.8.1 - only this specific version is listed as affected
-
Locate the streaming service libraryAccess the device filesystem via SSH, Telnet, or firmware extraction and search for the file libhipcam.so in the /lib or /usr/lib directoriesAffected if The libhipcam.so library file is present on the device, indicating the vulnerable streaming service component is installed
-
Verify the hardcoded credentials existExtract or examine the libhipcam.so binary and search within the file for static credential strings (usernames or passwords stored in plaintext)Affected if Hardcoded username and password strings are found embedded within the libhipcam.so binary - this confirms the vulnerability is present
A user is affected only if they have a Geeni GNC-CW013 doorbell running firmware version 1.8.1 with the libhipcam.so library containing hardcoded credentials.
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 dataPrimary remediation requires obtaining and deploying a firmware update from the vendor that removes the hardcoded credentials. As a compensating control, network-segment the device behind a firewall with restricted access, and monitor for unauthorized access attempts to the streaming service port.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-28999 — 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-2020-28999 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