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

> Remote attackers can bypass authentication on Dahua DVR appliances via UPnP replay attacks to gain unauthorized access.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-j3x8-8c44-4q7h

## What is CVE-2013-3613?

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

### Official description

Dahua DVR appliances do not properly restrict UPnP requests, which makes it easier for remote attackers to obtain access via vectors involving a replay attack against the TELNET port.

Weakness: CWE-287 (Improper Authentication)

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

It affects 65 products.


Products: Dahuasecurity Dvr0404hd-A, Dahuasecurity Dvr0404hd-L, Dahuasecurity Dvr0404hd-S, Dahuasecurity Dvr0404hd-U, Dahuasecurity Dvr0404hf-a-E, Dahuasecurity Dvr0404hf-Al-E, Dahuasecurity Dvr0404hf-S-E, Dahuasecurity Dvr0404hf-U-E, Dahuasecurity Dvr0804, Dahuasecurity Dvr0804hd-L, Dahuasecurity Dvr0804hd-S, Dahuasecurity Dvr0804hf-a-E, Dahuasecurity Dvr0804hf-Al-E, Dahuasecurity Dvr0804hf-L-E, Dahuasecurity Dvr0804hf-S-E, Dahuasecurity Dvr0804hf-U-E, Dahuasecurity Dvr1604hd-L, Dahuasecurity Dvr1604hd-S, Dahuasecurity Dvr1604hf-a-E, Dahuasecurity Dvr1604hf-Al-E and 45 more.

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

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

## Is CVE-2013-3613 being exploited?

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

Public exploit code:

- Dahua DVR 2.608.0000.0/2.608.GV00.0 - Authentication Bypass (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2013-3612](https://insights.sbomify.com/CVE-2013-3612/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2013-5754](https://insights.sbomify.com/CVE-2013-5754/): Auth bypass in n/a (critical 10.0)
- [CVE-2013-3614](https://insights.sbomify.com/CVE-2013-3614/): Weak cryptography in n/a (critical 9.3)
- [CVE-2013-3615](https://insights.sbomify.com/CVE-2013-3615/): Weak cryptography in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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