# CVE-2017-6343: Auth bypass in n/a

> Remote attackers can bypass authentication on Dahua NVR devices by using the MD5 admin hash, gaining unauthorized login access.

- **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:** 27 Feb 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mq4w-63hh-gh6j

## What is CVE-2017-6343?

CVE-2017-6343 is a high-severity authentication bypass vulnerability in n/a, published on 27 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The web interface on Dahua DHI-HCVR7216A-S3 devices with NVR Firmware 3.210.0001.10 2016-06-06, Camera Firmware 2.400.0000.28.R 2016-03-29, and SmartPSS Software 1.16.1 2017-01-19 allows remote attackers to obtain login access by leveraging knowledge of the MD5 Admin Hash without knowledge of the corresponding password, a different vulnerability than CVE-2013-6117.

Weakness: CWE-287 (Improper Authentication)

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

It affects 3 products.


Products: Dahuasecurity Camera Firmware, Dahuasecurity Nvr Firmware, Dahuasecurity Smartpss Firmware.

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

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

## Is CVE-2017-6343 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-6342](https://insights.sbomify.com/CVE-2017-6342/): Auth bypass in n/a (critical 9.8)
- [CVE-2017-6341](https://insights.sbomify.com/CVE-2017-6341/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-6343 is a high-severity authentication bypass vulnerability in n/a, published on 27 Feb 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-6343 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-6343/ (Markdown: https://insights.sbomify.com/CVE-2017-6343/index.md)
```

## Sources

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

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