DS-96xxxNI-Hx: Stack-based Buffer Overflow
CVE-2025-66177 is a high-severity stack-based buffer overflow vulnerability in DS-96xxxNI-Hx from Hikvision, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. Affected DS-96xxxNI-Hx versions: Build date before 250807. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.49% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of DS-96xxxNI-Hx you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on hikvision.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Hikvision | DS-96xxxNI-Hx | Build date before 250807 | Not stated |
| Hikvision | DS-96xxxNI-Ix | Build date before 250807 | Not stated |
| Hikvision | DS-96xxNXI-Sx | Build date before 250807 | Not stated |
| Hikvision | DS-96xxxNXI-Sx | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNXI-Mx/VPro | Build date before 250807 | Not stated |
| Hikvision | DS-96xxNXI-Mx/VPro | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNI-Mx | Build date before 250807 | Not stated |
| Hikvision | DS-77xxNI-Mx | Build date before 250807 | Not stated |
| Hikvision | DS-96xxNXI-Mx | Build date before 250807 | Not stated |
| Hikvision | DS-96xxxNXI-Mx | Build date before 250807 | Not stated |
| Hikvision | DS-86xxxNXI-Mx | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNXI-Ix/S | Build date before 250807 | Not stated |
| Hikvision | DS-77xxNXI-Ix/S | Build date before 250807 | Not stated |
| Hikvision | DS-86xxNXI-Ix/S | Build date before 250807 | Not stated |
| Hikvision | DS-96xxNXI-Ix/S | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNXI-Ix/VPro | Build date before 250807 | Not stated |
| Hikvision | DS-77xxNXI-Ix/VPro | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNXI-Kx(/xP) including(D)、(E)、(B) | Build date before 250807 | Not stated |
| Hikvision | DS-77xxNXI-Kx(/xP) including(D)、(E)、(B) | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNXI-Kx(/xP)/Vpro | Build date before 250807 | Not stated |
| Hikvision | DS-77xxNXI-Kx(/xP)/Vpro | Build date before 250807 | Not stated |
| Hikvision | DS-76xxNI-Qx(/xP) including(D)、(E) | Build date before 250807 | Not stated |
| Hikvision | DS-71xxNI-Q1(/xP)/M | Build date before 250807 | Not stated |
| Hikvision | DS-71xxNI-Q1(/xP) | Build date before 250807 | Not stated |
| Hikvision | DS-710xNI-G1/(xP)/M | Build date before 250807 | Not stated |
Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (hikvision.com).
Official description
There is a Buffer overflow Vulnerability in the device Search and Discovery feature of Hikvision NVR/DVR/CVR/IPC models. If exploited, an attacker on the same local area network (LAN) could cause the device to malfunction by sending specially crafted packets to an unpatched device.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Stack-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the stack.
How developers prevent this class of flaw
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Implement and perform bounds checking on input.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Stack-based Buffer Overflow vulnerabilities
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.6 High severity
Spotted an error? Tell us.