{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-46889 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-46889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-46889 is a medium-severity vulnerability in n/a, published on 23 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-46889 and fix it if it is affected.\n\nWhat it is: CVE-2023-46889 is a medium-severity vulnerability in n/a, published on 23 Jan 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-46889 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-2023-46889/ (Markdown: https://insights.sbomify.com/CVE-2023-46889/index.md)","id":"CVE-2023-46889","markdown":"https://insights.sbomify.com/CVE-2023-46889/index.md","name":"CVE-2023-46889","record":{"aliases":["GHSA-hr3c-fw3g-qvhf"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart Home Device","requires_auth":"none","summary":"An attacker can decrypt Wi-Fi credentials transmitted during the setup phase of the Meross MSH30Q device due to weak encryption implementation.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"msh30q_firmware","vendor":"meross"}],"cvss":{"score":5.7,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"Meross MSH30Q 4.5.23 is vulnerable to Cleartext Transmission of Sensitive Information. During the device setup phase, the MSH30Q creates an unprotected Wi-Fi access point. In this phase, MSH30Q needs to connect to the Internet through a Wi-Fi router. This is why MSH30Q asks for the Wi-Fi network name (SSID) and the Wi-Fi network password. When the user enters the password, the transmission of the Wi-Fi password and name between the MSH30Q and mobile application is observed in the Wi-Fi network. Although the Wi-Fi password is encrypted, a part of the decryption algorithm is public so we complemented the missing parts to decrypt it.","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":"Information disclosure in n/a","id":"CVE-2023-46889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2023-46892"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2023-46887"},"products":["n/a"],"published":"2024-01-23","related":[{"cvss_score":8.8,"headline":"Other in n/a","id":"CVE-2023-46892","kev_date_added":null,"published":"2024-01-23"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-17","vendors":["n/a"]},"summary":"An attacker can decrypt Wi-Fi credentials transmitted during the setup phase of the Meross MSH30Q device due to weak encryption implementation.","url":"https://insights.sbomify.com/CVE-2023-46889/"}