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

> Attackers can use default low-privilege credentials to list users and subsequently log in as admin, gaining full control of the IP camera.

- **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:** 30 Mar 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mqm7-jpjf-v8cm

## What is CVE-2017-7253?

CVE-2017-7253 is a high-severity authentication bypass vulnerability in n/a, published on 30 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dahua IP Camera devices 3.200.0001.6 can be exploited via these steps: 1. Use the default low-privilege credentials to list all users via a request to a certain URI. 2. Login to the IP camera with admin credentials so as to obtain full control of the target IP camera. During exploitation, the first JSON object encountered has a "Component error: login challenge!" message. The second JSON object encountered has a result indicating a successful admin login.

Weakness: CWE-922 (Insecure Storage of Sensitive Information)

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

It affects 1 product.


Products: Dahuasecurity Ip Camera Firmware.

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

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

## Is CVE-2017-7253 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-3223](https://insights.sbomify.com/CVE-2017-3223/): Memory corruption in IP Camera (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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