The Amcrest IP2M-841B V2.520.AC00.18.R, Dahua IPC-XXBXX V2.622.0000000.9.R, Dahua IPC HX5X3X and HX4X3X V2.800.0000008.0.R, Dahua DH-IPC HX8
Noroxi assessment
Priority: Monitor (action score 38/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 25% (FIRST EPSS); higher than 97.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; 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 · FIRST EPSS
The Amcrest IP2M-841B V2.520.AC00.18.R, Dahua IPC-XXBXX V2.622.0000000.9.R, Dahua IPC HX5X3X and HX4X3X V2.800.0000008.0.R, Dahua DH-IPC HX883X and DH-IPC-HX863X V2.622.0000000.7.R, Dahua DH-SD4XXXXX V2.623.0000000.7.R, Dahua DH-SD5XXXXX V2.623.0000000.1.R, Dahua DH-SD6XXXXX V2.640.0000000.2.R and V2.623.0000000.1.R, Dahua NVR5XX-4KS2 V3.216.0000006.0.R, Dahua NVR4XXX-4KS2 V3.216.0000006.0.R, and NVR2XXX-4KS2 do not require authentication to access the HTTP endpoint /videotalk. An unauthenticated, remote person can connect to this endpoint and potentionally listen to the audio of the capturing device.
- Published
- Jul 29, 2019
- Updated
- Jun 16, 2026
- EPSS
- 25.0% · 98th percentile
- CWE
- CWE-306
Report tools
Action score
38
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 8 / 30 · 25.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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 | ip2m-841b firmware | cpe:2.3:o:amcrest:ip2m-841b_firmware |
| amcrest | ip2m-841b | cpe:2.3:h:amcrest:ip2m-841b |
| dahua | dh-ipc-hx863x | cpe:2.3:o:dahua:dh-ipc-hx863x |
| dahua | dh-ipc-hx883x | cpe:2.3:o:dahua:dh-ipc-hx883x |
| dahua | dh-sd4xxxxx | cpe:2.3:o:dahua:dh-sd4xxxxx |
| dahua | dh-sd5xxxxx | cpe:2.3:o:dahua:dh-sd5xxxxx |
| dahua | dh-sd6xxxxx | cpe:2.3:o:dahua:dh-sd6xxxxx |
| dahua | ipc-hx4x3x | cpe:2.3:o:dahua:ipc-hx4x3x |
| dahua | ipc-hx5x3x | cpe:2.3:o:dahua:ipc-hx5x3x |
| dahua | ipc-xxbxx | cpe:2.3:o:dahua:ipc-xxbxx |
| dahua | nvr2xxx-4ks2 | cpe:2.3:o:dahua:nvr2xxx-4ks2 |
| dahua | nvr4xxx-4ks2 | cpe:2.3:o:dahua:nvr4xxx-4ks2 |
and 1 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- dahua dh-ipc-hx863xbefore 2018-05-18
- dahua dh-ipc-hx883xbefore 2018-05-18
- dahua dh-sd4xxxxxbefore 2018-05-18
- dahua dh-sd5xxxxxbefore 2018-05-18
- dahua dh-sd6xxxxxbefore 2018-05-18
- dahua ipc-hx4x3xbefore 2018-05-18
- dahua ipc-hx5x3xbefore 2018-05-18
- dahua ipc-xxbxxbefore 2018-05-18
- dahua nvr2xxx-4ks2before 2018-05-18
- dahua nvr4xxx-4ks2before 2018-05-18
- dahua nvr5xxx-4ks2before 2018-05-18
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 Dahua DH-IPC HX883X and DH-IPC-HX863X
- V2.622.0000000.7.Raffected
n/a Dahua DH-SD4XXXXX
- V2.623.0000000.7.Raffected
n/a Dahua DH-SD5XXXXX
- V2.623.0000000.1.Raffected
n/a Dahua DH-SD6XXXXX
- V2.640.0000000.2.R and V2.623.0000000.1.Raffected
n/a Dahua IPC HX5X3X and HX4X3X
- V2.800.0000008.0.Raffected
n/a Dahua IPC-XXBXX
- V2.622.0000000.9.Raffected
n/a Dahua NVR4XXX-4KS2
- V3.216.0000006.0.R and NVR2XXX-4KS2affected
n/a Dahua NVR5XX-4KS2
- V3.216.0000006.0.Raffected
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
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
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 | webapps | 2019-07-30 |
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.
- Published
- First PoCsame day
- TodayOct 15, 2026+2635 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.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-306 · Missing Authentication for Critical FunctionCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Root cause
A function added for development or support ships to production without authentication. It often relies on the assumption that it is “only reachable from the internal network.”
The bug in code
The whole CWE-306 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
// Added for the support teamapp.post("/maintenance/reset", resetDevice);Fixed
if (config.maintenanceEnabled) { app.post( "/maintenance/reset", requireSession, requireRole("admin"), resetDevice );}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
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.