CVE-2020-9529
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 · uneditedFirmware developed by Shenzhen Hichip Vision Technology (V6 through V20), as used by many different vendors in millions of Internet of Things devices, suffers from a privilege escalation vulnerability that allows attackers on the local network to reset the device's administrator password. This affects products marketed under the following brand names: Accfly, Alptop, Anlink, Besdersec, BOAVISION, COOAU, CPVAN, Ctronics, D3D Security, Dericam, Elex System, Elite Security, ENSTER, ePGes, Escam, FLOUREON, GENBOLT, Hongjingtian (HJT), ICAMI, Iegeek, Jecurity, Jennov, KKMoon, LEFTEK, Loosafe, Luowice, Nesuniq, Nettoly, ProElite, QZT, Royallite, SDETER, SV3C, SY2L, Tenvis, ThinkValue, TOMLOV, TPTEK, WGCC, and ZILINK.
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 privilege escalation vulnerability in Shenzhen Hichip Vision Technology firmware (versions V6 through V20) allows authenticated or unauthenticated attackers on the local network to reset the device administrator password, effectively granting full control over the affected IoT 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< 2020-06-29CVSS 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 manufacturerAccess the device web interface or check network discovery results (e.g., ONVIF, RTSP, HTTP) to confirm the vendor is Shenzhen Hichip Vision Technology. Look for Hichip Vision, Hichip, or associated branding in the web UI or device mDNS/UPnP responses.Affected if The device is manufactured by Shenzhen Hichip Vision Technology and exposes a web management interface on the local network.
-
Check the firmware versionLog into the device web interface and navigate to the System or Device Info section to view the firmware build date or version number. Alternatively, query the device HTTP API (commonly /cgi-bin/config/get?channel=0 or similar endpoint) for firmware version information.Affected if The firmware version is dated before 2020-06-29, or displays a version in the V6 to V20 range indicating it is older than the patched build.
-
Verify the password reset function is accessibleAttempt to access the device password reset or recovery endpoint over HTTP from the local network. Common paths include /cgi-bin/user/reset or /rpc/password_reset. Check if the web service responds without requiring authentication or accepts unauthenticated password reset requests.Affected if The device password reset endpoint is reachable over the local network without requiring valid administrator credentials.
-
Confirm local network exposureReview network configuration to verify the device web interface (typically HTTP/HTTPS on ports 80, 443, or 8080) is accessible from the local network segment where attacker access is possible. Check firewall rules and device IP address assignment.Affected if The device web management interface is accessible from an untrusted or shared local network segment without network isolation.
A user is affected if their device is a Shenzhen Hichip Vision Technology product running firmware dated before 2020-06-29 (versions V6-V20) with the web-based password reset functionality exposed to an untrusted local network segment.
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.
dbcve · scoped2020-06-29
Isolate affected devices on restricted network segments, limit local network access, and apply vendor-provided firmware updates when available. If no update exists, consider device replacement.
Any firmware version dated 2020-06-29 or later from the device vendor
- Identify the specific device model and vendor from the affected brand list
- Visit the vendor's official support or downloads page for your device
- Locate and download the latest firmware version released on or after June 29, 2020
- Consult the vendor's firmware update instructions (typically involves accessing the device's web interface or using a firmware upgrade tool)
- Upload and apply the firmware update to the device via the method specified by the vendor
- After the update completes and the device reboots, access the device's admin interface
- Change the default administrator password to a strong, unique password
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9529 — 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-9529 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