CVE-2017-3223
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 · uneditedDahua IP camera products using firmware versions prior to V2.400.0000.14.R.20170713 include a version of the Sonia web interface that may be vulnerable to a stack buffer overflow. Dahua IP camera products include an application known as Sonia (/usr/bin/sonia) that provides the web interface and other services for controlling the IP camera remotely. Versions of Sonia included in firmware versions prior to DH_IPC-Consumer-Zi-Themis_Eng_P_V2.408.0000.11.R.20170621 do not validate input data length for the 'password' field of the web interface. A remote, unauthenticated attacker may submit a crafted POST request to the IP camera's Sonia web interface that may lead to out-of-bounds memory operations and loss of availability or remote code execution. The issue was originally identified by the researcher in firmware version DH_IPC-HX1X2X-Themis_EngSpnFrn_N_V2.400.0000.30.R.20160803.
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 IP camera firmware contains a stack buffer overflow vulnerability in the Sonia web interface (/usr/bin/sonia). The password field in the web interface does not validate input length, allowing a remote unauthenticated attacker to submit a crafted POST request with an oversized password value that overwrites stack memory, potentially leading to remote code execution or denial of service.
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_ipc-ack-themis_eng_p_v2.400.0000.14.r.20170713.bin< 2.400.0000.14.r.20170713CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 device model and manufacturerAccess the camera's web interface or check the device label/metadata to confirm it is a Dahua IP camera. Use the device's administrative console or examine DHCP/DNS entries to identify the device.Affected if The device is not a Dahua IP camera, then it is not affected by this specific vulnerability.
-
Determine the installed firmware versionLog into the camera's web interface and navigate to the 'System' or 'About' page to view the firmware version. Alternatively, use the camera's API or firmware release file name if accessible.Affected if The firmware version is lower than 2.400.0000.14.r.20170713, then the device may be affected.
-
Verify the Sonia web interface is exposedAttempt to access the '/usr/bin/sonia' endpoint or the main login page of the camera's web interface over HTTP/HTTPS from the network.Affected if The Sonia web interface is reachable over the network, then the vulnerable component is exposed.
-
Check for unauthenticated access to the login endpointSend a POST request to the login endpoint with an oversized password value (e.g., a string exceeding normal password length) and observe the response. A successful exploit may cause a crash or abnormal behavior.Affected if The login endpoint accepts unauthenticated POST requests without proper length validation, then the vulnerability is present.
If the device is a Dahua IP camera running firmware version lower than 2.400.0000.14.r.20170713 and the Sonia web interface is accessible, the environment is likely affected by CVE-2017-3223.
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.
dbcve · scoped2.400.0000.14.r.20170713
Update Dahua IP camera firmware to version V2.400.0000.14.R.20170713 or later. If patching is not immediately possible, restrict network access to the camera's web interface via firewall rules or VLAN segmentation to limit exposure to unauthenticated attackers.
V2.400.0000.14.R.20170713 or later; Consumer-Zi models: V2.408.0000.11.R.20170621 or later
- 1. Identify the specific Dahua IP camera model number
- 2. Download the latest firmware from Dahua's official support website (dhilink.com or dahuatech.com)
- 3. Access the camera's web interface and navigate to the firmware upgrade section
- 4. Upload the firmware file (e.g., dh_ipc-ack-themis_eng_p_v2.400.0000.14.r.20170713.bin or later)
- 5. Wait for the upgrade to complete - do not power off the device
- 6. After reboot, verify the firmware version in the system information page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3223 — 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-3223 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