# CVE-2017-17747: Missing authorization in n/a

> Remote attackers can trigger a denial of service by accessing the logout functionality without proper authentication on TP-Link switches.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 20 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7j8g-5mr3-5j66

## What is CVE-2017-17747?

CVE-2017-17747 is a medium-severity missing authorization vulnerability in n/a, published on 20 Dec 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Weak access controls in the Device Logout functionality on the TP-Link TL-SG108E v1.0.0 allow remote attackers to call the logout functionality, triggering a denial of service condition.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Tp-Link Tl-Sg108e Firmware.

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

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

## Is CVE-2017-17747 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8074](https://insights.sbomify.com/CVE-2017-8074/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-8075](https://insights.sbomify.com/CVE-2017-8075/): Information disclosure in n/a (critical 9.8)
- [CVE-2017-8076](https://insights.sbomify.com/CVE-2017-8076/): Weak cryptography in n/a (critical 9.8)
- [CVE-2017-8077](https://insights.sbomify.com/CVE-2017-8077/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2017-17746](https://insights.sbomify.com/CVE-2017-17746/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-17747 is a medium-severity missing authorization vulnerability in n/a, published on 20 Dec 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-17747 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-17747/ (Markdown: https://insights.sbomify.com/CVE-2017-17747/index.md)
```

## Sources

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

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