CVE-2025-52601
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 · uneditedCybersecurity Nozomi Networks Labs, a specialized security company focused on Industrial Control Systems (ICS) and OT/IoT security, has discovered a vulnerability in Device Manager that a hardcoded encryption key for sensitive information. An attacker can use key to decrypt sensitive information. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.
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 hardcoded encryption key was discovered in the Device Manager component. This static cryptographic key, embedded in the firmware, can be extracted by an attacker and used to decrypt sensitive information that was protected using this key, leading to potential confidentiality breaches.
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< 2.24.00< 2.24.00< 2.24.00< 2.24.00< 2.24.00< 2.24.00< 2.24.00< 2.24.00CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 Hanwhavision device modelLocate the physical device label or access the device web interface or management console to determine the exact model number (e.g., Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnb 8002, Xno 9082rz, Xnv 9082r, Xnd 9082rf)Affected if The model matches any of the affected models listed in the CVE (Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnd 8082rv, Xnb 8002, Xno 9082rz, Xnv 9082r, Xnd 9082rf)
-
Check the installed firmware versionAccess the device web interface under System > Information or use the Device Manager software to view the firmware version. Alternatively, use the device CLI or API if available to query the firmware versionAffected if The firmware version is lower than 2.24.00 (e.g., 2.23.x, 2.22.x, etc.)
-
Confirm the Device Manager component is in useVerify that the Device Manager component is installed and active on the device. This is typically the central management interface for the device. Check the device management software or web interface for the Device Manager statusAffected if Device Manager component is present and running on the affected firmware version
-
Assess network exposure of the deviceReview network configuration to determine if the Device Manager interface is accessible from untrusted networks. Check firewall rules, port exposures, and ACLs governing access to the device management portsAffected if The device management interface is exposed to the internet or untrusted networks, making extraction of the hardcoded key more feasible for remote attackers
The environment is affected if the device model is one of the listed Hanwhavision models and the firmware version is below 2.24.00, indicating the hardcoded encryption key is present in the Device Manager component.
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.24.00
Apply the vendor-released patch firmware from Nozomi Networks to replace the hardcoded key with properly managed encryption keys. Until patched, minimize network exposure of affected Device Manager instances and monitor for unauthorized access.
Firmware 2.24.00
- 1. Identify the specific device model (Xno 8082r, Xnv 8082r, Xnd 8082rf, Xnd 8082rv, Xnb 8002, Xno 9082rz, Xnv 9082r, or Xnd 9082rf) from the affected product list
- 2. Access the device management interface or console
- 3. Navigate to the firmware update or system settings section
- 4. Obtain the firmware version 2.24.00 or later from the manufacturer (Hanwha Vision)
- 5. Upload and apply the new firmware following the manufacturer's upgrade procedure
- 6. Verify the firmware version has been successfully updated to 2.24.00 or later
- 7. Confirm the hardcoded encryption key vulnerability has been remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing6.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 $6,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52601 — 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-52601 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