{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3405 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3405 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3405 is a medium-severity vulnerability in 360F5, published on 11 Jan 2021."},"fix_prompt":"Check this codebase for CVE-2019-3405 and fix it if it is affected.\n\nWhat it is: CVE-2019-3405 is a medium-severity vulnerability in 360F5, published on 11 Jan 2021. \nExploitation: There is no known exploitation of CVE-2019-3405 in the wild and no public exploit code.\n\nAffected product: 360F5. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-3405/ (Markdown: https://insights.sbomify.com/CVE-2019-3405/index.md)","id":"CVE-2019-3405","markdown":"https://insights.sbomify.com/CVE-2019-3405/index.md","name":"CVE-2019-3405","record":{"aliases":["GHSA-rfv6-w65g-9xh7"],"analysis":null,"analysis_generated_by":null,"assigner":"360ST","cpe":[{"product":"360f5_firmware","vendor":"360"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"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","id":"CVE-2019-3405","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in ZTE WF820+ LTE Outdoor CPE","id":"CVE-2019-3409"},"packages":[],"prev":{"headline":"Auth bypass in 360 Router F5C","id":"CVE-2019-3404"},"products":["360F5"],"published":"2021-01-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2019-3405/"}