{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6402 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6402 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6402 is a high-severity vulnerability in n/a, published on 14 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6402 and fix it if it is affected.\n\nWhat it is: CVE-2018-6402 is a high-severity vulnerability in n/a, published on 14 Apr 2020. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-6402 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-6402/ (Markdown: https://insights.sbomify.com/CVE-2018-6402/index.md)","id":"CVE-2018-6402","markdown":"https://insights.sbomify.com/CVE-2018-6402/index.md","name":"CVE-2018-6402","record":{"aliases":["GHSA-j5q8-22j2-m58f"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ecobee smart thermostat","requires_auth":"none","summary":"Attackers can force Ecobee devices to connect to unencrypted Wi-Fi networks, bypassing configured WPA2 encryption settings via Evil Twin attacks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ecobee4_firmware","vendor":"ecobee"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Ecobee Ecobee4 4.2.0.171 devices can be forced to deauthenticate and connect to an unencrypted Wi-Fi network with the same SSID, even if the device settings specify use of encryption such as WPA2, as long as the competing network has a stronger signal. An attacker must be able to set up a nearby SSID, similar to an \"Evil Twin\" attack.","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":"Security feature bypass in n/a","id":"CVE-2018-6402","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-6405"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-6401"},"products":["n/a"],"published":"2020-04-14","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can force Ecobee devices to connect to unencrypted Wi-Fi networks, bypassing configured WPA2 encryption settings via Evil Twin attacks.","url":"https://insights.sbomify.com/CVE-2018-6402/"}