dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
1080 Lite 8ch FirmwareOperating system · Amcrest

CVE-2020-5735

HIGH · 8.8 CVSS v3.1 Published 2020-04-08
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
In the wild Public exploit 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
Amcrest cameras and NVR are vulnerable to a stack-based buffer overflow over port 37777. An authenticated remote attacker can abuse this issue to crash the device and possibly execute arbitrary code.

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

Amcrest cameras and NVR devices contain a stack-based buffer overflow vulnerability in the network service listening on port 37777. An authenticated remote attacker can send specially crafted packets to trigger the overflow, potentially allowing code execution or causing device denial of service.

MitigationApply vendor firmware updates when available; restrict network access to port 37777 to authorized management stations; ensure strong authentication credentials are in place to limit 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
1080 Lite 8ch FirmwareOperating system
Affected:all versions
Amdv10814 H5 FirmwareOperating system
Affected:all versions
Ipm 721 FirmwareOperating system
Affected:< v2.420.ac00.18.r.20200217
Ip2m 841 FirmwareOperating system
Affected:< v2.420.ac00.18.r.20200217
Ip2m 841 V3 FirmwareOperating system
Affected:< v2.800.0000000.6.r.200314
Ip2m 853ew FirmwareOperating system
Affected:< v2.623.00ac004.0.r.200316
Ip2m 858w FirmwareOperating system
Affected:< v2.623.00ac004.0.r.200316
Ip2m 866w FirmwareOperating system
Affected:< v2.623.00ac004.0.r.200316

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Amcrest devices on your network
    Scan your network for devices responding on port 37777/tcp, or review your asset inventory for Amcrest cameras and NVRs with model numbers matching the affected list (1080 Lite 8ch, Amdv10814 H5, Ipm 721, Ip2m 841, Ip2m 841 V3, Ip2m 853ew, Ip2m 858w, Ip2m 866w)
    Affected if Any Amcrest device from the affected model list is present on your network and port 37777 is accessible
  2. Verify port 37777 exposure
    From an external or untrusted network perspective, attempt to reach port 37777 on your Amcrest devices using telnet or nc (e.g., nc -zv <device_ip> 37777). Review firewall rules to confirm whether port 37777 is exposed to untrusted networks.
    Affected if Port 37777 is open and reachable from networks outside your trusted administrative zone
  3. Check installed firmware version
    Access the Amcrest device web interface or RTSP stream, navigate to Settings > System > About, or use the Amcrest SmartPSS client to retrieve the firmware version. Compare the version string against the affected ranges: Ipm 721/Ip2m 841 (< v2.420.ac00.18.r.20200217), Ip2m 841 V3 (< v2.800.0000000.6.r.200314), Ip2m 853ew/858w/866w (< v2.623.00ac004.0.r.200316). For 1080 Lite 8ch and Amdv10814 H5, all versions are affected.
    Affected if The installed firmware version falls within the affected ranges or the device is a 1080 Lite 8ch or Amdv10814 H5 model (all versions)
  4. Confirm authentication is enabled
    Verify that the device has strong authentication credentials configured for the web interface and RTSP access. Check if the default admin password has been changed and review user account settings in the device configuration.
    Affected if Authentication is disabled or weak credentials are in use (since the vulnerability requires authenticated access)

Your environment is affected if you have any Amcrest devices from the listed models with accessible port 37777 and a firmware version within the affected ranges (or a 1080 Lite 8ch/Amdv10814 H5 at any version), especially if port 37777 is exposed to untrusted networks.

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

Apply vendor firmware updates when available; restrict network access to port 37777 to authorized management stations; ensure strong authentication credentials are in place to limit exploitation.

Recommended fix Moderate confidence

Firmware v2.420.ac00.18.r.20200217 or later for IPM-721/IP2M-841; v2.800.0000000.6.r.200314 for IP2M-841 V3; v2.623.00ac004.0.r.200316 for IP2M-853ew/858w/866w; contact vendor for 1080 Lite 8ch and Amdv10814 H5

  1. 1. Identify the specific Amcrest device model and current firmware version from the web interface or API
  2. 2. For IPM-721 devices: Navigate to Settings > System > Upgrade and apply firmware version v2.420.ac00.18.r.20200217 or later
  3. 3. For IP2M-841 devices: Navigate to Settings > System > Upgrade and apply firmware version v2.420.ac00.18.r.20200217 or later
  4. 4. For IP2M-841 V3 devices: Navigate to Settings > System > Upgrade and apply firmware version v2.800.0000000.6.r.200314 or later
  5. 5. For IP2M-853ew, IP2m-858w, and IP2m-866w devices: Navigate to Settings > System > Upgrade and apply firmware version v2.623.00ac004.0.r.200316 or later
  6. 6. For 1080 Lite 8ch and Amdv10814 H5 (all versions): Contact Amcrest technical support for available firmware updates, as no fixed version is specified in advisory sources
  7. 7. After upgrade, verify the new firmware version is applied and the device is operational
  8. 8. Restrict access to port 37777 using firewall rules or network segmentation to limit attack surface until patching is complete
Caveat Firmware upgrades on embedded devices may reset configuration; backup settings before upgrading and verify device compatibility with your integration requirements

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

Fix this in 1080 Lite 8ch Firmware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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