# CVE-2019-3405: In the 3.1.3.64296 and lower version of 360F5, the third party can trigger the device to send a deauth frame by constructing and sending a s


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 11 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rfv6-w65g-9xh7

## What is CVE-2019-3405?

CVE-2019-3405 is a medium-severity vulnerability in 360F5, published on 11 Jan 2021. 

### Official description

In the 3.1.3.64296 and lower version of 360F5, the third party can trigger the device to send a deauth frame by constructing and sending a specific illegal 802.11 Null Data Frame, which will cause other wireless terminals connected to disconnect from the wireless, so as to attack the router wireless by DoS. At present, the vulnerability has been effectively handled, and users can fix the vulnerability after updating the firmware version.

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

It affects 1 product.


Products: 360 360f5 Firmware.

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

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

## Is CVE-2019-3405 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-3405 is a medium-severity vulnerability in 360F5, published on 11 Jan 2021. 
Exploitation: There is no known exploitation of CVE-2019-3405 in the wild and no public exploit code.

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

## Sources

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

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