# CVE-2017-8219: Denial of service in n/a

> Attackers can crash the HTTP server on TP-Link C2 and C20i cameras by sending a crafted Cookie header to a specific URI.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 25 Apr 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pr33-m33x-xpgg

## What is CVE-2017-8219?

CVE-2017-8219 is a medium-severity denial of service vulnerability in n/a, published on 25 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TP-Link C2 and C20i devices through firmware 0.9.1 4.2 v0032.0 Build 160706 Rel.37961n allow DoSing the HTTP server via a crafted Cookie header to the /cgi/ansi URI.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Tp-Link C20i Firmware, Tp-Link C2 Firmware.

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

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

## Is CVE-2017-8219 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8220](https://insights.sbomify.com/CVE-2017-8220/): Command injection in n/a (critical 9.9)
- [CVE-2017-8218](https://insights.sbomify.com/CVE-2017-8218/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8217](https://insights.sbomify.com/CVE-2017-8217/): Misconfiguration in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8219 is a medium-severity denial of service vulnerability in n/a, published on 25 Apr 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-8219 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-8219/ (Markdown: https://insights.sbomify.com/CVE-2017-8219/index.md)
```

## Sources

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

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