# CVE-2017-14263: Missing authorization in n/a

> Remote attackers can create admin accounts by reusing guest session IDs, leading to full device control.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g8vq-9qgg-p683

## What is CVE-2017-14263?

CVE-2017-14263 is a high-severity missing authorization vulnerability in n/a, published on 11 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2017-14263?

It affects 7 products.


Products: Honeywell Enterprise Dvr Firmware, Honeywell Fusion Iv Rev C Firmware, Honeywell Maxpro Nvr Hybrid Se Firmware, Honeywell Maxpro Nvr Hybrid Xe Firmware, Honeywell Maxpro Nvr Pe Firmware, Honeywell Maxpro Nvr Se Firmware, Honeywell Maxpro Nvr Xe Firmware.

## How do I fix CVE-2017-14263?

No fix has been published for CVE-2017-14263 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-14263 being exploited?

There is no known exploitation of CVE-2017-14263 in the wild and no public exploit code.

Public exploit code:

- https://github.com/zzz66686/CVE-2017-14263 (github_poc): https://github.com/zzz66686/CVE-2017-14263

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14263 and fix it if it is affected.

What it is: CVE-2017-14263 is a high-severity missing authorization vulnerability in n/a, published on 11 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-14263 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-14263/ (Markdown: https://insights.sbomify.com/CVE-2017-14263/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-14263
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-14263
- OSV: https://osv.dev/vulnerability/CVE-2017-14263

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-14263/
Summaries are generated and may contain mistakes; the official description above is the record.