# CVE-2018-7580: Denial of service in n/a

> An attacker can freeze the Philips Hue hub by sending a SYN flood, rendering lights and cloud services unresponsive until the attack stops.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Dec 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vq7v-82fm-4659

## What is CVE-2018-7580?

CVE-2018-7580 is a high-severity denial of service vulnerability in n/a, published on 21 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Philips Hue is vulnerable to a Denial of Service attack. Sending a SYN flood on port tcp/80 will freeze Philips Hue's hub and it will stop responding. The "hub" will stop operating and be frozen until the flood stops. During the flood, the user won't be able to turn on/off the lights, and all of the hub's functionality will be unresponsive. The cloud service also won't work with the hub.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2018-7580?

It affects 1 product.


Products: Philips Hue Firmware.

## How do I fix CVE-2018-7580?

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

## Is CVE-2018-7580 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7580 and fix it if it is affected.

What it is: CVE-2018-7580 is a high-severity denial of service vulnerability in n/a, published on 21 Dec 2020. 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-2018-7580 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-2018-7580/ (Markdown: https://insights.sbomify.com/CVE-2018-7580/index.md)
```

## Sources

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

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