# CVE-2019-3404: Auth bypass in 360 Router F5C

> Attackers can bypass authentication to access background CGI functions on 360 routers by manipulating URI fields.

- **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:** 4 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rp5q-hh57-wxgx

## What is CVE-2019-3404?

CVE-2019-3404 is a high-severity authentication bypass vulnerability in 360 Router F5C, published on 4 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

By adding some special fields to the uri ofrouter app function, the user could abuse background app cgi functions withoutauthentication. This affects 360 router P0 and F5C.

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

It affects 2 products.


Products: 360 F5c Router Firmware, 360 P0 Router Firmware.

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

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

## Is CVE-2019-3404 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3404 is a high-severity authentication bypass vulnerability in 360 Router F5C, published on 4 Mar 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-2019-3404 in the wild and no public exploit code.

Affected product: 360 Router F5C. 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-3404/ (Markdown: https://insights.sbomify.com/CVE-2019-3404/index.md)
```

## Sources

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

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