CVE-2025-66177
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 · uneditedThere 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.
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 confidenceBuffer overflow vulnerability in Hikvision NVR/DVR/CVR/IPC device Search and Discovery feature allows an attacker on the same local area network to cause device malfunction by sending specially crafted packets to an unpatched device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 Hikvision devices on your networkUse network scanning tools (e.g., nmap, Angry IP Scanner) to discover devices with Hikvision vendor identifiers, or manually inspect device labels, web interfaces, or management consoles for NVR/DVR/CVR/IPC modelsAffected if Any Hikvision NVR, DVR, CVR, or IPC device is found on the network
-
Confirm Search and Discovery feature is activeCheck the device web interface or configuration panel for the 'Device Search', 'Search and Discovery', or 'UPnP/SSDP discovery' feature status. This is typically found under Network Settings or System MaintenanceAffected if The Search and Discovery feature is enabled on the device
-
Verify network accessibility of the devicePing the device IP address or check if ports used by the discovery service (typically 8000, 8080, or 554 for RTSP) are open and reachable from your local network segmentAffected if The device responds to network requests from your local subnet
-
Determine the device firmware versionAccess the device web interface, go to System or Maintenance section, and locate the firmware version displayed. Compare this version against any Hikvision security advisories for CVE-2025-66177Affected if The installed firmware version matches or predates the unpatched version referenced in Hikvision security documentation
-
Check for similar devices in the same network segmentReview your network topology or DHCP lease tables to identify all devices sharing the same subnet as the Hikvision device, as the attack requires LAN adjacencyAffected if Multiple Hikvision devices or other network devices exist on the same broadcast domain
You are affected if you have any Hikvision NVR/DVR/CVR/IPC devices with the Search and Discovery feature enabled and accessible from your local network, and the device firmware has not been patched to address CVE-2025-66177.
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 dataApply vendor-provided firmware/security patches to all affected Hikvision devices and consider network segmentation to restrict LAN-based attacks to critical infrastructure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66177 — 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-2025-66177 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