NVD / CVE Program· CNA dahua

CVE-2020-9499: Some Dahua products have buffer overflow vulnerabilities.

Noroxi assessment

Priority: Monitor (action score 28/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.5% (FIRST EPSS); higher than 74.2% of all records.
Anyone who can reach it over the internet can trigger it. Administrator privileges are 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

Some Dahua products have buffer overflow vulnerabilities. After the successful login of the legal account, the attacker sends a specific DDNS test command, which may cause the device to go down.

HighCVSS 7.2 · v3.1—No exploit No fix recorded

Memory safety

Published: Apr 9, 2020
Updated: Jun 16, 2026
EPSS: 1.5% · 74th percentile
CWE: CWE-120

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 28 / 40 · 7.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.5%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
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

Is your version affected? Check it

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 help

Affected 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
dahua	n54a4p	cpe:2.3:h:dahua:n54a4p
dahuasecurity	sd6al firmware	cpe:2.3:o:dahuasecurity:sd6al_firmware
dahuasecurity	sd6al	cpe:2.3:h:dahuasecurity:sd6al
dahuasecurity	sd5a firmware	cpe:2.3:o:dahuasecurity:sd5a_firmware
dahuasecurity	sd5a	cpe:2.3:h:dahuasecurity:sd5a
dahuasecurity	sd1a firmware	cpe:2.3:o:dahuasecurity:sd1a_firmware
dahuasecurity	sd1a	cpe:2.3:h:dahuasecurity:sd1a
dahuasecurity	ptz1a firmware	cpe:2.3:o:dahuasecurity:ptz1a_firmware
dahuasecurity	ptz1a	cpe:2.3:h:dahuasecurity:ptz1a
dahuasecurity	sd50 firmware	cpe:2.3:o:dahuasecurity:sd50_firmware
dahuasecurity	sd50	cpe:2.3:h:dahuasecurity:sd50
dahuasecurity	sd52c firmware	cpe:2.3:o:dahuasecurity:sd52c_firmware

and 26 more

Using n54a4p? Add it to your stack and be the first to know about CVEs like this one. (IP camera)

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

dahuasecurity ipc-hx2xxx firmwarebefore 2019-12
dahuasecurity ipc-hx5842h firmwarebefore 2019-12
dahuasecurity ipc-hx7842h firmwarebefore 2019-12
dahuasecurity ipc-hxxx5x4x firmwarebefore 2019-12
dahuasecurity n42b1p firmwarebefore 2019-12
dahuasecurity n42b2p firmwarebefore 2019-12
dahuasecurity n42b3p firmwarebefore 2019-12
dahuasecurity n52a4p firmwarebefore 2019-12
dahuasecurity n52b2p firmwarebefore 2019-12
dahuasecurity n52b3p firmwarebefore 2019-12
dahuasecurity n52b5p firmwarebefore 2019-12
dahuasecurity n54a4p firmwarebefore 2019-12
dahuasecurity n54b2p firmwarebefore 2019-12
dahuasecurity ptz1a firmwarebefore 2019-12
dahuasecurity sd1a firmwarebefore 2019-12
dahuasecurity sd50 firmwarebefore 2019-12
dahuasecurity sd52c firmwarebefore 2019-12
dahuasecurity sd5a firmwarebefore 2019-12
dahuasecurity sd6al firmwarebefore 2019-12

Versions reported by the vendor

Affected version ranges reported by the assigning authority (dahua). Independent of NVD's CPE analysis and usually ahead of it.

n/a IPC-HX2XXX Series,IPC-HXXX5X4X Series,IPC-HX5842H,IPC-HX7842H,NVR 5x Series,NVR 4x Series,SD6AL Series,SD5A Series,SD1A Series,PTZ1A Series,SD50/52C Series
- Versions which Build time before December,2019affected

Same product

dahua: all records

Other highest-scoring records for the same primary product.

CVE-2020-9500Some products of Dahua have Denial of Service vulnerabilities.
19Monitor

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

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

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 researchers

Finders, 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.
Administrator privileges are required.
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: High
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

When data is copied, the source length is not compared with the size of the destination buffer. Excess data overwrites adjacent memory.

The bug in code

The whole CWE-120 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1char buf[256];
2memcpy(buf, pkt->data, pkt->len);

Fixed

1char buf[256];
2if (pkt->len > sizeof(buf)) {
3  return -EINVAL;
4}
5memcpy(buf, pkt->data, pkt->len);

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

www.dahuasecurity.com/support/cybersecurity/details/727

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records