# CVE-2013-6117: Auth bypass in n/a

> Remote attackers can bypass authentication on Dahua DVRs to steal credentials, modify passwords, and clear logs via TCP port 37777.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f492-fgmp-2462

## What is CVE-2013-6117?

CVE-2013-6117 is a high-severity authentication bypass vulnerability in n/a, published on 11 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dahua DVR 2.608.0000.0 and 2.608.GV00.0 allows remote attackers to bypass authentication and obtain sensitive information including user credentials, change user passwords, clear log files, and perform other actions via a request to TCP port 37777.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-6117?

It affects 1 product.


Products: Dahuasecurity Dvr Firmware.

## How do I fix CVE-2013-6117?

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

## Is CVE-2013-6117 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6117 exists.

Public exploit code:

- CVE-2013-6117 (github_poc): https://github.com/milo2012/CVE-2013-6117
- Dahua DVR 2.608.0000.0/2.608.GV00.0 - Authentication Bypass (Metasploit) (exploitdb)
- Improved Metasploit module for CVE-2013-6117 (Dahua DVR authentication bypass) (github_poc): https://github.com/fsn4k3/dahua-dvr-metasploit
- Dahua DVR Auth Bypass Scanner (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6117 and fix it if it is affected.

What it is: CVE-2013-6117 is a high-severity authentication bypass vulnerability in n/a, published on 11 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6117 exists.

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-2013-6117/ (Markdown: https://insights.sbomify.com/CVE-2013-6117/index.md)
```

## Sources

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

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