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

> Attackers can view video and audio streams without authentication on TP-Link NC250 cameras by accessing a specific RTSP URL.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-876q-g9p3-g7pr

## What is CVE-2017-10796?

CVE-2017-10796 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On TP-Link NC250 devices with firmware through 1.2.1 build 170515, anyone can view video and audio without authentication via an rtsp://admin@yourip:554/h264_hd.sdp URL.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Tp-Link Nc250 Firmware.

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

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

## Is CVE-2017-10796 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-10796 is a medium-severity authentication bypass vulnerability in n/a, published on 2 Jul 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-10796 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-10796/ (Markdown: https://insights.sbomify.com/CVE-2017-10796/index.md)
```

## Sources

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

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