CVE-2020-5735: Amcrest cameras and NVR are vulnerable to a stack-based buffer overflow over port 37777.
Noroxi assessment
Priority: This week (action score 76/100)
- CISA has confirmed exploitation in the wild (Nov 3, 2021). Remediation deadline for US federal agencies: May 3, 2022.
- Probability of exploitation in the next 30 days: 36.2% (FIRST EPSS); higher than 98.4% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Don’t wait for the next maintenance window. Until a fix is released, restrict access to the affected component and follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS
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.
- Published
- Apr 8, 2020
- Updated
- Jun 16, 2026
- EPSS
- 36.2% · 98th percentile
- CWE
- CWE-121
Report tools
Action score
76
This week
Don’t wait for the next maintenance window.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 30 / 30 · Listed
- EPSS
- 11 / 30 · 36.2%
CISA SSVC decision
- Exploitation
- active
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Actively exploited in the wild
CISA added this to its Known Exploited Vulnerabilities catalog on Nov 3, 2021. That signals real attacks, not theory.
Remediation deadline for US federal agencies: May 3, 2022.
Get told when this record changes
- In CISA KEV: exploitation in the wild confirmed
- Weaponized exploit exists
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| amcrest | 1080-lite 8ch firmware | cpe:2.3:o:amcrest:1080-lite_8ch_firmware |
| amcrest | 1080-lite 8ch | cpe:2.3:h:amcrest:1080-lite_8ch |
| amcrest | amdv10814-h5 firmware | cpe:2.3:o:amcrest:amdv10814-h5_firmware |
| amcrest | amdv10814-h5 | cpe:2.3:h:amcrest:amdv10814-h5 |
| amcrest | ipm-721 firmware | cpe:2.3:o:amcrest:ipm-721_firmware |
| amcrest | ipm-721 | cpe:2.3:h:amcrest:ipm-721 |
| amcrest | ip2m-841 firmware | cpe:2.3:o:amcrest:ip2m-841_firmware |
| amcrest | ip2m-841 | cpe:2.3:h:amcrest:ip2m-841 |
| amcrest | ip2m-841-v3 firmware | cpe:2.3:o:amcrest:ip2m-841-v3_firmware |
| amcrest | ip2m-841-v3 | cpe:2.3:h:amcrest:ip2m-841-v3 |
| amcrest | ip2m-853ew firmware | cpe:2.3:o:amcrest:ip2m-853ew_firmware |
| amcrest | ip2m-853ew | cpe:2.3:h:amcrest:ip2m-853ew |
and 24 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- amcrest 1080-lite 8ch firmwareall versions
- amcrest amdv10814-h5 firmwareall versions
- amcrest ip2m-841 firmwarebefore v2.420.ac00.18.r.20200217
- amcrest ip2m-841-v3 firmwarebefore v2.800.0000000.6.r.200314
- amcrest ip2m-853ew firmwarebefore v2.623.00ac004.0.r.200316
- amcrest ip2m-858w firmwarebefore v2.623.00ac004.0.r.200316
- amcrest ip2m-866ew firmwarebefore v2.623.00ac004.0.r.200316
- amcrest ip2m-866w firmwarebefore v2.623.00ac004.0.r.200316
- amcrest ip4m-1053ew firmwarebefore v2.623.00ac004.0.r.200316
- amcrest ip8m-2454ew firmwarebefore v2.622.00ac000.0.r.200320
- amcrest ip8m-2493eb firmwarebefore v2.622.00ac000.0.r.200320
- amcrest ip8m-2496eb firmwarebefore v2.622.00ac000.0.r.200320
- amcrest ip8m-2597e firmwarebefore v2.800.00ac000.0.r.200330
- amcrest ip8m-mb2546ew firmwarebefore v2.622.00ac000.0.r.200320
- amcrest ip8m-mt2544ew firmwarebefore v2.622.00ac000.0.r.200320
- amcrest ip8m-t2499ew firmwarebefore v2.622.00ac000.0.r.200320
- amcrest ipm-721 firmwarebefore v2.420.ac00.18.r.20200217
- amcrest ipm-hx1 firmwarebefore v2.420.ac00.18.r.20200217
Versions reported by the vendor
Affected version ranges reported by the assigning authority (tenable). Independent of NVD's CPE analysis and usually ahead of it.
n/a Amcrest
- before 2.623.00AC004.0.R.200316, 2.420.AC00.18.R.20200217, 2.800.00AC000.0.R.200330, 2.800.0000000.6.R.200314.bin, 2.622.00AC000.0.R.200320.bin, and 4.000.00AC000.0.R.200218affected
Same product
amcrest: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-5736Amcrest cameras and NVR are vulnerable to a null pointer dereference over port 37777.26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
Weaponized
A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | dos | 2020-04-08 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoCsame day
- Published
- CISA KEV+574 d
- TodayOct 28, 2026+2394 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-121 · Stack-based Buffer OverflowCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.