# CVE-2019-18980: Missing authorization in n/a

> Remote attackers can control smart bulb operations without authentication due to an unprotected API, requiring only network access.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 14 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-wf72-r867-38x7

## What is CVE-2019-18980?

CVE-2019-18980 is a high-severity missing authorization vulnerability in n/a, published on 14 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Signify Philips Taolight Smart Wi-Fi Wiz Connected LED Bulb 9290022656 devices, an unprotected API lets remote users control the bulb's operation. Anyone can turn the bulb on or off, or change its color or brightness remotely. There is no authentication or encryption to use the control API. The only requirement is that the attacker have network access to the bulb.

Weakness: CWE-311 (Missing Encryption of Sensitive Data), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2019-18980?

It affects 1 product.


Products: Philips Taolight Smart Wi-Fi Wiz Connected Led Bulb 9290022656 Firmware.

## How do I fix CVE-2019-18980?

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

## Is CVE-2019-18980 being exploited?

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

Public exploit code:

- WiZ smart bulb LAN security tool - auto-discovery, CVE-tagged audit, intel recon & device control. Extends CVE-2019-18980 to new hardware. No credentials required. (github_poc): https://github.com/anmolksachan/wiz-bulb-tool

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18980 and fix it if it is affected.

What it is: CVE-2019-18980 is a high-severity missing authorization vulnerability in n/a, published on 14 Nov 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-2019-18980 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-2019-18980/ (Markdown: https://insights.sbomify.com/CVE-2019-18980/index.md)
```

## Sources

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

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