CVE-2017-14263
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 · uneditedHoneywell NVR devices allow remote attackers to create a user account in the admin group by leveraging access to a guest account to obtain a session ID, and then sending that session ID in a userManager.addUser request to the /RPC2 URI. The attacker can login to the device with that new user account to fully control the 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 · high confidenceHoneywell NVR devices contain an authentication bypass vulnerability where an attacker with guest account access can obtain a valid session ID and use it in a userManager.addUser request to the /RPC2 URI, allowing creation of a new administrative user account and full device control.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 the device label/documentation to determine the exact model. Common Honeywell NVR models include Enterprise DVR, Maxpro NVR (Hybrid SE/XE, SE, XE, PE), and Fusion IV Rev C.Affected if The device model matches one of the affected products: Honeywell Enterprise Dvr, Maxpro Nvr Hybrid Se, Maxpro Nvr Hybrid Xe, Maxpro Nvr Se, Maxpro Nvr Xe, Fusion Iv Rev C, or Maxpro Nvr Pe.
-
Confirm firmware versionLog into the device web interface and navigate to System > Information or System > Maintenance to view the firmware version. Alternatively, check via the device's built-in diagnostics or serial console if available.Affected if The firmware version is any version (all versions of the affected products are vulnerable).
-
Verify guest account statusLog into the device web interface and navigate to User Management or Account Settings. Check if a guest or limited user account is enabled or exists on the system.Affected if A guest account or limited-privilege user account is enabled or present on the device.
-
Check for unauthorized administrative accountsIn the device web interface under User Management, review all user accounts with Administrator or Supervisor privileges. Look for any accounts that were not created by the legitimate administrator.Affected if There are administrative accounts present that were not created by the authorized administrator, indicating possible exploitation.
-
Inspect device network exposureCheck if the device web interface (HTTP/HTTPS on ports 80, 443, or custom ports) is accessible from untrusted networks. Review firewall rules and network segmentation.Affected if The device web interface is exposed to untrusted networks, allowing remote attackers to attempt the guest account authentication bypass.
If the device is one of the listed Honeywell NVR models with a guest or limited user account enabled and accessible over the network, it is vulnerable to this authentication bypass. The presence of unexpected administrative accounts may indicate the vulnerability has been exploited.
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 firmware patches when available and restrict guest account access; implement proper session authorization checks ensuring userManagement functions require administrative authentication.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14263 — 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-14263 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