# CVE-2017-8403: Auth bypass in n/a

> Attackers can bypass authentication via Bluetooth to change Wi-Fi passwords and gain full REST access to 360fly 4K cameras.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 1 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mj7g-945c-pf2g

## What is CVE-2017-8403?

CVE-2017-8403 is a high-severity authentication bypass vulnerability in n/a, published on 1 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

360fly 4K cameras allow unauthenticated Wi-Fi password changes and complete access with REST by using the Bluetooth Low Energy pairing procedure, which is available at any time and does not require a password. This affects firmware 2.1.4. Exploitation can use the 360fly Android or iOS application, or the BlueZ gatttool program.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: 360fly 4k Camera Firmware.

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

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

## Is CVE-2017-8403 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8403 is a high-severity authentication bypass vulnerability in n/a, published on 1 May 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-8403 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-8403/ (Markdown: https://insights.sbomify.com/CVE-2017-8403/index.md)
```

## Sources

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

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