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

> Remote attackers can bypass authentication on the FTP server to modify system files and gain root control of the device.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-m7v9-w9c3-mw2g

## What is CVE-2017-16566?

CVE-2017-16566 is a critical authentication bypass vulnerability in n/a, published on 17 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

On Jooan IP Camera A5 2.3.36 devices, an insecure FTP server does not require authentication, which allows remote attackers to read or replace core system files including those used for authentication (such as passwd and shadow). This can be abused to take full root level control of the device.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Qacctv Jooan A5 Ip Camera Firmware.

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

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

## Is CVE-2017-16566 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16566 is a critical authentication bypass vulnerability in n/a, published on 17 Nov 2017. 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-2017-16566 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-16566/ (Markdown: https://insights.sbomify.com/CVE-2017-16566/index.md)
```

## Sources

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

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