{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-50692 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-50692 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-50692 is a medium-severity vulnerability in n/a, published on 24 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-50692 and fix it if it is affected.\n\nWhat it is: CVE-2024-50692 is a medium-severity vulnerability in n/a, published on 24 Jan 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-50692 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-2024-50692/ (Markdown: https://insights.sbomify.com/CVE-2024-50692/index.md)","id":"CVE-2024-50692","markdown":"https://insights.sbomify.com/CVE-2024-50692/index.md","name":"CVE-2024-50692","record":{"aliases":["GHSA-gxmw-34m7-64r8"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Solar inverter controller","requires_auth":"low_privilege","summary":"Hardcoded MQTT credentials allow attackers to send arbitrary commands to solar inverters and impersonate the broker via MitM attacks.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"winet-s_firmware","vendor":"sungrowpower"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"SunGrow WiNet-SV200.001.00.P027 and earlier versions contains hardcoded MQTT credentials that allow an attacker to send arbitrary commands to an arbitrary inverter. It is also possible to impersonate the broker, because TLS is not used to identify the real MQTT broker. This means that MQTT communications are vulnerable to MitM attacks at the TCP/IP level.","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":"Hardcoded credentials in n/a","id":"CVE-2024-50692","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2024-50693"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2024-50691"},"products":["n/a"],"published":"2025-01-24","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-50694","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-50695","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-50698","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":8.1,"headline":"Memory corruption in n/a","id":"CVE-2024-50697","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":7.5,"headline":"Supply chain in n/a","id":"CVE-2024-50696","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":6.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-50690","kev_date_added":null,"published":"2025-01-24"}],"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-02-06","vendors":["n/a"]},"summary":"Hardcoded MQTT credentials allow attackers to send arbitrary commands to solar inverters and impersonate the broker via MitM attacks.","url":"https://insights.sbomify.com/CVE-2024-50692/"}