# CVE-2019-5014: Missing authorization in Winco Firefly

> An attacker can bypass access controls on the Winco Firefly fireworks controller via Bluetooth Low Energy to trigger improper access control vulnerabilities.

- **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:** 8 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rvfv-gfcw-5592

## What is CVE-2019-5014?

CVE-2019-5014 is a medium-severity missing authorization vulnerability in Winco Firefly, published on 8 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An exploitable improper access control vulnerability exists in the bluetooth low energy functionality of Winco Fireworks FireFly FW-1007 V2.0. An attacker can connect to the device to trigger this vulnerability.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Wincofireworks Fw-1007 Firmware.

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

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

## Is CVE-2019-5014 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-5014 is a medium-severity missing authorization vulnerability in Winco Firefly, published on 8 May 2019. 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-2019-5014 in the wild and no public exploit code.

Affected product: Winco Firefly. 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-5014/ (Markdown: https://insights.sbomify.com/CVE-2019-5014/index.md)
```

## Sources

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

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