# CVE-2017-7923: Hardcoded credentials in Hikvision Cameras

> Attackers can exploit hardcoded credentials in configuration files to escalate privileges and access sensitive information on Hikvision cameras.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2017
- **Updated:** 27 Dec 2024
- **Also known as:** GHSA-m7r5-29r2-m6xh

## What is CVE-2017-7923?

CVE-2017-7923 is a high-severity vulnerability in Hikvision Cameras, published on 6 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Password in Configuration File issue was discovered in Hikvision DS-2CD2xx2F-I Series V5.2.0 build 140721 to V5.4.0 build 160530, DS-2CD2xx0F-I Series V5.2.0 build 140721 to V5.4.0 Build 160401, DS-2CD2xx2FWD Series V5.3.1 build 150410 to V5.4.4 Build 161125, DS-2CD4x2xFWD Series V5.2.0 build 140721 to V5.4.0 Build 160414, DS-2CD4xx5 Series V5.2.0 build 140721 to V5.4.0 Build 160421, DS-2DFx Series V5.2.0 build 140805 to V5.4.5 Build 160928, and DS-2CD63xx Series V5.0.9 build 140305 to V5.3.5 Build 160106 devices. The password in configuration file vulnerability could allow a malicious user to escalate privileges or assume the identity of another user and access sensitive information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-260 (Password in Configuration File)

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

It affects 58 products.


Products: Hikvision Ds-2cd2032-I Firmware, Hikvision Ds-2cd2112-I Firmware, Hikvision Ds-2cd2132-I Firmware, Hikvision Ds-2cd2212-I5 Firmware, Hikvision Ds-2cd2232-I5 Firmware, Hikvision Ds-2cd2312-I Firmware, Hikvision Ds-2cd2332-I Firmware, Hikvision Ds-2cd2412f-I\(w\) Firmware, Hikvision Ds-2cd2432f-I\(w\) Firmware, Hikvision Ds-2cd2512f-I\(s\) Firmware, Hikvision Ds-2cd2532f-I\(s\) Firmware, Hikvision Ds-2cd2612f-I\(s\) Firmware, Hikvision Ds-2cd2632f-I\(s\) Firmware, Hikvision Ds-2cd2712f-I\(s\) Firmware, Hikvision Ds-2cd2732f-I\(s\) Firmware, Hikvision Ds-2cd2t32-I3 Firmware, Hikvision Ds-2cd2t32-I5 Firmware, Hikvision Ds-2cd2t32-I8 Firmware, Hikvision Ds-2cd4012f-\(A\) Firmware, Hikvision Ds-2cd4012f-\(P\) Firmware and 38 more.

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

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

## Is CVE-2017-7923 being exploited?

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

## Other vulnerabilities in Hikvision Cameras

- [CVE-2017-7921](https://insights.sbomify.com/CVE-2017-7921/): Hikvision Multiple Products Improper Authentication (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7923 is a high-severity vulnerability in Hikvision Cameras, published on 6 May 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7923 in the wild and no public exploit code.

Affected product: Hikvision Cameras. 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-7923/ (Markdown: https://insights.sbomify.com/CVE-2017-7923/index.md)
```

## Sources

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

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