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

> Attackers can view live video feeds without authentication because the RTSP service does not enforce login by default, exposing private footage.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 2 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fq2q-8mq9-5rfh

## What is CVE-2017-8405?

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

### Official description

An issue was discovered on D-Link DCS-1130 and DCS-1100 devices. The binary rtspd in /sbin folder of the device handles all the rtsp connections received by the device. It seems that the binary loads at address 0x00012CF4 a flag called "Authenticate" that indicates whether a user should be authenticated or not before allowing access to the video feed. By default, the value for this flag is zero and can be set/unset using the HTTP interface and network settings tab as shown below. The device requires that a user logging to the HTTP management interface of the device to provide a valid username and password. However, the device does not enforce the same restriction by default on RTSP URL due to the checkbox unchecked by default, thereby allowing any attacker in possession of external IP address of the camera to view the live video feed. The severity of this attack is enlarged by the fact that there more than 100,000 D-Link devices out there.

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Dlink Dcs-1100 Firmware, Dlink Dcs-1130 Firmware.

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

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

## Is CVE-2017-8405 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1599](https://insights.sbomify.com/CVE-2013-1599/): Command injection in n/a (critical 9.8)
- [CVE-2017-8410](https://insights.sbomify.com/CVE-2017-8410/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8415](https://insights.sbomify.com/CVE-2017-8415/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8412](https://insights.sbomify.com/CVE-2017-8412/): Memory corruption in n/a (high 8.8)
- [CVE-2017-8413](https://insights.sbomify.com/CVE-2017-8413/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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