cve.bz

CVE-2017-14263 honeywell: Session Fixation

8.1 highEPSS 3.7%

High (8.1) in honeywell. EPSS 3.7% estimated probability of exploitation activity in the next 30 days.

On this page
Honeywell 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.

Severity

CVSS 3.0

8.1 high
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
3.7% (unchanged from 3.7% a week ago; 3.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 90th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-384 Session Fixation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2017-14263 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-14263?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-14263?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-14263 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Attack patterns (CAPEC)

  • CAPEC-21 Exploitation of Trusted Identifiers Likelihood: High · Severity: High
  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-39 Manipulating Opaque Client-based Data Tokens Likelihood: High · Severity: Medium
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-61 Session Fixation Likelihood: Medium · Severity: High
  • CAPEC-196 Session Credential Falsification through Forging Likelihood: Medium · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON