CVE-2017-9314
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 · uneditedAuthentication 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.
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 confidenceDahua NVR devices NVR50XX, NVR52XX, NVR54XX, and NVR58XX contain an authentication bypass vulnerability in versions prior to DH_NVR5xxx_Eng_P_V2.616.0000.0.R.20171102. Attackers can exploit this by forging JSON messages to gain unauthorized access to additional operations beyond their authorized privileges.
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 data< dh_nvr5464_eng_p_v2.616.0000.0.r.20171102< dh_nvr5208_eng_p_v2.616.0000.0.r.20171102< dh_nvr5432_eng_p_v2.616.0000.0.r.20171102< dh_nvr5416_eng_p_v2.616.0000.0.r.20171102< dh_nvr5464_eng_p_v2.616.0000.0.r.20171102< dh_nvr5432_eng_p_v2.616.0000.0.r.20171102< dh_nvr5416_eng_p_v2.616.0000.0.r.20171102< dh_nvr5232_eng_p_v2.616.0000.0.r.20171102CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the NVR device modelAccess the device web interface or check the physical device label to determine if the model is one of the affected series: NVR50XX, NVR52XX, NVR54XX, or NVR58XX (specifically models 5208, 5216, 5232, 5416, 5432, 5464, or 5484)Affected if The device is a Dahua NVR from the NVR5xxx series listed in the affected products
-
Check the firmware versionLog into the NVR web interface and navigate to the System Info or About page to view the installed firmware version (typically labeled as something like dh_nvr5xxx_eng_p_v2.xxx)Affected if The installed firmware version is earlier than dh_nvr5xxx_eng_p_v2.616.0000.0.r.20171102 for the specific model
-
Verify remote access is enabledCheck the NVR network settings to confirm that remote access via HTTP/HTTPS is enabled, as the vulnerability is exploited through JSON messages sent to the deviceAffected if Remote access or the web interface is exposed to the network
-
Confirm JSON API endpoint accessibilityAttempt to access the device JSON API endpoint (typically port 80/443) by sending a test request to see if the device responds to JSON-based commandsAffected if The device JSON API is accessible over the network and responds to unauthenticated or specially crafted JSON messages
If the device is a Dahua NVR5xxx model with firmware version earlier than dh_nvr5xxx_eng_p_v2.616.0000.0.r.20171102 and has its web interface or JSON API exposed to the network, the device is affected by this authentication bypass vulnerability.
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 dataUpgrade Dahua NVR firmware to version DH_NVR5xxx_Eng_P_V2.616.0000.0.R.20171102 or later. If immediate patching is not possible, restrict network access to NVR devices and monitor for suspicious JSON-based API requests.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9314 — 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-2017-9314 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