CVE-2017-9314
N/A
Published: November 13, 2017 at 04:00 PM UTC
Updated: June 17, 2026 at 01:27 AM UTC
48 products affected across 2 vendorsNvr5232-4ks2 FirmwareNvr5816-4ks2 FirmwareNvr5832-16p 4KS2 Firmware
Using NVR50XX, VR52XX, VR54XX, VR58XX by Dahua Technologies?
Get instant alerts when new vulnerabilities affect NVR50XX, VR52XX, VR54XX, VR58XX - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.9%
Description
Authentication vulnerability found in Dahua NVR models NVR50XX, NVR52XX, NVR54XX, NVR58XX with software before DH_NVR5xxx_Eng_P_V2.616.0000.0.R.20171102. Attacker could exploit this vulnerability to gain access to additional operations by means of forging json message.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
v < dh_nvr5208_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5208_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5208-4ks2 (same device)
v < dh_nvr5208_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5208_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5208-8p-4ks2 (same device)
v < dh_nvr5216_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5216_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5216-16p-4ks2 (same device)
v < dh_nvr5216_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5216_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5216-4ks2 (same device)
v < dh_nvr5216_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5216_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5216-8p-4ks2 (same device)
v < dh_nvr5224_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5224_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5224-24p-4ks2 (same device)
v < dh_nvr5232_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5232_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5232-16p-4ks2 (same device)
v < dh_nvr5232_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5232_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5232-4ks2 (same device)
v < dh_nvr5232_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5232_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5232-8p-4ks2 (same device)
v < dh_nvr5416_eng_p_v2.616.0000.0.r.20171102
Affected range stops below dh_nvr5416_eng_p_v2.616.0000.0.r.20171102, so it looks safe — our inference, not a vendor statement
dahuasecurity-nvr5416-16p-4ks2 (same device)
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
References (1)
x_refsource_CONFIRMIssue TrackingVendor Advisory
Source: [email protected]
http://www.dahuasecurity.com/annoucementsingle/security-advisory--authentication-vulnerability-found-in-some-dahua-nvr_14731_211.htmlQuick Info
StatusMODIFIED
CWE
CWE-287
Get alerted
Stop reading CVE feeds looking for your own stack
Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.
Free plan, no card