CVE-2025-46352
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 · uneditedThe CS5000 Fire Panel is vulnerable due to a hard-coded password that runs on a VNC server and is visible as a string in the binary responsible for running VNC. This password cannot be altered, allowing anyone with knowledge of it to gain remote access to the panel. Such access could enable an attacker to operate the panel remotely, potentially putting the fire panel into a non-functional state and causing serious safety issues.
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 confidenceThe CS5000 Fire Panel contains a hard-coded, unchangeable VNC password embedded as a plaintext string in the firmware binary. This password provides unauthenticated remote access to the fire panel's VNC server, allowing attackers to operate the panel remotely and potentially disable fire safety monitoring capabilities.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/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.
-
Confirm CS5000 Fire Panel modelIdentify the device model through physical label, management interface, or system documentationAffected if Device is not a CS5000 Fire Panel (this CVE does not apply)
-
Check if VNC server is enabledInspect the fire panel configuration or running services to determine if VNC server functionality is active; examine network listening ports for 5900 or related VNC portsAffected if VNC server is disabled or not present on the system
-
Verify firmware accessibilityObtain a copy of the device firmware binary through vendor downloads, firmware update mechanism, or legitimate extraction methodAffected if Firmware binary cannot be obtained for analysis
-
Search firmware for hardcoded VNC passwordUse binary analysis tools (strings, grep, hex editors) to search the firmware binary for plaintext VNC-related credentials, password strings, or known VNC authentication patternsAffected if Firmware binary contains plaintext VNC password strings that cannot be changed by administrators
-
Assess network exposure of VNC serviceReview firewall rules, network segmentation, and accessible ports to determine if the VNC service (port 5900) is reachable from untrusted network segmentsAffected if VNC service is exposed to untrusted networks without network-level access controls
A system is affected if it is a CS5000 Fire Panel with VNC enabled, running firmware that contains a hardcoded plaintext VNC password accessible in the binary, and the VNC service 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 dataIsolate the fire panel network from untrusted networks using firewalls or air-gapping; block VNC ports (typically 5900) at network boundaries; engage vendor for firmware update to remove hard-coded credentials.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46352 — 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-46352 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