CVE-2020-5736
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 · uneditedAmcrest cameras and NVR are vulnerable to a null pointer dereference over port 37777. An authenticated remote attacker can abuse this issue to crash the device.
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 confidenceAmcrest IP cameras and NVR devices contain a null pointer dereference vulnerability on port 37777 (the default RTSP port). An authenticated remote attacker can send specially crafted requests to crash the device, resulting in denial of service.
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 dataall versionsall versions< v2.420.ac00.18.r.20200217< v2.420.ac00.18.r.20200217< v2.800.0000000.6.r.200314< v2.623.00ac004.0.r.200316< v2.623.00ac004.0.r.200316< v2.623.00ac004.0.r.200316CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 Amcrest devices on the networkScan for devices listening on port 37777 (the default RTSP port). Use nmap: nmap -p 37777 -sV <target_range> or check firewall logs for traffic on this port.Affected if Port 37777 is open and responds, indicating an Amcrest camera or NVR device.
-
Confirm the device modelAccess the device web interface, check DHCP logs, or use ONVIF discovery tools to identify the exact Amcrest model number. Cross-reference with the affected product list.Affected if The device is one of: 1080 Lite 8ch, Amdv10814 H5, Ipm 721, Ip2m 841, Ip2m 841 V3, Ip2m 853ew, Ip2m 858w, or Ip2m 866w.
-
Check the installed firmware versionLog into the Amcrest web interface and navigate to the System or About section to view the firmware version. Alternatively, use RTSP or ONVIF queries to retrieve firmware information.Affected if The firmware version falls within the affected ranges: Ipm 721/Ip2m 841 below v2.420.ac00.18.r.20200217, Ip2m 841 V3 below v2.800.0000000.6.r.200314, or Ip2m 853ew/858w/866w below v2.623.00ac004.0.r.200316, or any version for 1080 Lite 8ch/Amdv10814 H5.
-
Verify if default credentials are in useAttempt to authenticate to the device using the default Amcrest credentials (typically admin:admin or admin:123456). Check if the login succeeds without modification.Affected if Default credentials have not been changed, allowing authenticated remote attackers to exploit the vulnerability.
A user is affected if they have an Amcrest device from the affected model list with a vulnerable firmware version, port 37777 exposed, and default credentials still active.
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 dataRestrict network access to port 37777 using firewalls or VLANs, change default credentials to prevent unauthorized access, and check vendor firmware updates for patches.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5736 — 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-5736 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