CVE-2017-16725
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 · uneditedA Stack-based Buffer Overflow issue was discovered in Xiongmai Technology IP Cameras and DVRs using the NetSurveillance Web interface. The stack-based buffer overflow vulnerability has been identified, which may allow an attacker to execute code remotely or crash the device. After rebooting, the device restores itself to a more vulnerable state in which Telnet is accessible.
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 · moderate confidenceA stack-based buffer overflow vulnerability exists in Xiongmai Technology IP cameras and DVRs via the NetSurveillance Web interface. This flaw allows remote attackers to execute arbitrary code or crash the affected device. The vulnerability is particularly concerning as the device reverts to an even more vulnerable state after reboot, enabling Telnet access.
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= 4.02.r11.3070= 4.02.r11.3070= 4.02.r11.3070= 4.02.r11.7601= 4.02.r11.7601= 4.02.r11.7601= 4.02.r11.7601= 4.02.r11.7601CVSS 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 modelAccess the device web interface or check device labeling to confirm it is a Xiongmaitech model (Ahb7008f8 H, Ahb7008f4 H, Ahb7008f2 H, Ahb7008t Mh V2, Ahb7004t Mh V2, Ahb7004t H V2, Ahb7016t Lm V2, or Ahb7008t Lm V2)Affected if The device is one of these eight models
-
Check the firmware versionLog into the device web interface (NetSurveillance) and navigate to System > System Info or Device Info to view the firmware versionAffected if The firmware version matches exactly 4.02.r11.3070 or 4.02.r11.7601
-
Confirm NetSurveillance Web interface is exposedAttempt to access the device web interface on port 80 or 8080 from the network segment where the device is deployedAffected if The NetSurveillance Web interface is reachable from an untrusted network segment
-
Check Telnet service status after rebootAfter rebooting the device, attempt to connect to port 23 (Telnet) to determine if the service becomes availableAffected if Telnet port 23 becomes accessible after a device reboot
The device is affected if it is one of the eight listed Xiongmai models running firmware version 4.02.r11.3070 or 4.02.r11.7601, and the NetSurveillance Web interface is network-accessible.
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 dataImplement network segmentation to isolate camera/DVR systems from untrusted networks, block external access to the web interface and Telnet ports (23), and contact Xiongmai for firmware patches. If no patch is available, consider device replacement.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16725 — 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-16725 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