dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2020-36873

HIGH · 8.7 CVSS v4.0 Published 2025-11-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
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
Astak CM-818T3 2.4GHz wireless security surveillance cameras contain an unauthenticated configuration disclosure vulnerability in the /web/cgi-bin/hi3510/backup.cgi endpoint. The endpoint permits remote download of a compressed configuration backup without requiring authentication or authorization. The exposed backup may include administrative credentials and other sensitive device settings, enabling an unauthenticated remote attacker to obtain information that could facilitate further compromise of the camera or connected network.

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 Astak CM-818T3 camera has an unauthenticated configuration disclosure vulnerability in the /web/cgi-bin/hi3510/backup.cgi endpoint. This CGI script allows any remote attacker to download a compressed configuration backup without any authentication, exposing administrative credentials and sensitive device settings in plaintext.

MitigationRestrict network access to the camera's web interface via firewall or network segmentation. If available, apply vendor firmware updates. Otherwise, consider replacing the device or implementing strict access controls on the network layer.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 device model
    Access the camera's web interface or check the device label/documentation to confirm it is an Astak CM-818T3 camera
    Affected if The device is an Astak CM-818T3 camera or uses the same firmware base
  2. Confirm web interface accessibility
    Attempt to reach the camera's IP address on ports 80 or 443 via HTTP
    Affected if The camera's web interface is reachable from the network being tested
  3. Test the vulnerable endpoint
    Send an HTTP GET request to http://[camera-ip]/web/cgi-bin/hi3510/backup.cgi
    Affected if The endpoint returns a response without requiring any authentication credentials
  4. Verify configuration backup is downloadable
    Check if the response from backup.cgi contains a compressed archive or configuration data
    Affected if The endpoint returns a downloadable file or configuration data without authentication
  5. Check for credential exposure
    Extract and inspect the downloaded backup file for plaintext administrative credentials
    Affected if The backup file contains username/password pairs or other sensitive settings in plaintext

A user is affected if they have an Astak CM-818T3 camera with the /web/cgi-bin/hi3510/backup.cgi endpoint accessible without authentication and the device returns a configuration backup.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict network access to the camera's web interface via firewall or network segmentation. If available, apply vendor firmware updates. Otherwise, consider replacing the device or implementing strict access controls on the network layer.

Recommended fix Low confidence
  1. Isolate the affected camera on a dedicated VLAN or network segment to limit exposure to other critical systems
  2. Configure firewall rules to block external/untrusted network access to the camera's web interface (ports 80/443)
  3. If the camera's web interface must be accessible internally, implement IP whitelisting or VPN-based access control
  4. Disable UPnP on the camera and network router to prevent automatic port forwarding
  5. Monitor network traffic for attempts to access /web/cgi-bin/hi3510/backup.cgi or similar configuration endpoints
  6. Consider replacing the Astak CM-818T3 with a newer camera model from a vendor that provides regular security updates
  7. If continued use is required, contact Astak vendor support to inquire about firmware updates addressing this vulnerability
Caveat Embedded IoT devices like this camera may have limited or no firmware update options; replacement may be necessary

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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