{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2018-15479 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-15479 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-15479 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-15479 and fix it if it is affected.\n\nWhat it is: CVE-2018-15479 is a medium-severity authentication bypass vulnerability in n/a, published on 30 Aug 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-15479 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-15479/ (Markdown: https://insights.sbomify.com/CVE-2018-15479/index.md)","id":"CVE-2018-15479","markdown":"https://insights.sbomify.com/CVE-2018-15479/index.md","name":"CVE-2018-15479","record":{"aliases":["GHSA-2v7m-c8xh-937p"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"myStrom WiFi devices","requires_auth":"none","summary":"Attackers can impersonate myStrom IoT devices by guessing MAC addresses due to missing device-to-cloud authentication, allowing unauthorized control.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wifi_bulb_firmware","vendor":"mystrom"},{"product":"wifi_button_firmware","vendor":"mystrom"},{"product":"wifi_button_plus_firmware","vendor":"mystrom"},{"product":"wifi_led_strip_firmware","vendor":"mystrom"},{"product":"wifi_switch_eu_firmware","vendor":"mystrom"},{"product":"wifi_switch_firmware","vendor":"mystrom"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"An issue was discovered in myStrom WiFi Switch V1 before 2.66, WiFi Switch V2 before 3.80, WiFi Switch EU before 3.80, WiFi Bulb before 2.58, WiFi LED Strip before 3.80, WiFi Button before 2.73, and WiFi Button Plus before 2.73. Devices did not authenticate themselves to the cloud in device to cloud communication. This lack of device authentication allowed an attacker to impersonate any device by guessing or learning their MAC address.","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":"Auth bypass in n/a","id":"CVE-2018-15479","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Business logic in n/a","id":"CVE-2018-15480"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2018-15478"},"products":["n/a"],"published":"2018-08-30","related":[{"cvss_score":8.8,"headline":"Business logic in n/a","id":"CVE-2018-15480","kev_date_added":null,"published":"2018-08-30"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2018-15476","kev_date_added":null,"published":"2018-08-30"},{"cvss_score":8.1,"headline":"Auth bypass in n/a","id":"CVE-2018-15478","kev_date_added":null,"published":"2018-08-30"}],"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 impersonate myStrom IoT devices by guessing MAC addresses due to missing device-to-cloud authentication, allowing unauthorized control.","url":"https://insights.sbomify.com/CVE-2018-15479/"}