{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-50684 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-50684 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-50684 is a medium-severity vulnerability in n/a, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-50684 and fix it if it is affected.\n\nWhat it is: CVE-2024-50684 is a medium-severity vulnerability in n/a, published on 26 Feb 2025. 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-2024-50684 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-50684/ (Markdown: https://insights.sbomify.com/CVE-2024-50684/index.md)","id":"CVE-2024-50684","markdown":"https://insights.sbomify.com/CVE-2024-50684/index.md","name":"CVE-2024-50684","record":{"aliases":["GHSA-rmc5-w442-6f93"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"iSolarCloud Android app","requires_auth":"none","summary":"Attackers can decrypt intercepted communications between the iSolarCloud Android app and server due to an insecure AES key with insufficient entropy.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"isolarcloud","vendor":"sungrowpower"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"SunGrow iSolarCloud Android app V2.1.6.20241017 and prior uses an insecure AES key to encrypt client data (insufficient entropy). This may allow attackers to decrypt intercepted communications between the mobile app and iSolarCloud.","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":"Weak cryptography in n/a","id":"CVE-2024-50684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2024-50685"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-50677"},"products":["n/a"],"published":"2025-02-26","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2024-50688","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2024-50685","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2024-50686","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2024-50687","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2024-50689","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2024-50693","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":7.4,"headline":"Security feature bypass in n/a","id":"CVE-2024-50691","kev_date_added":null,"published":"2025-02-26"}],"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-03-05","vendors":["n/a"]},"summary":"Attackers can decrypt intercepted communications between the iSolarCloud Android app and server due to an insecure AES key with insufficient entropy.","url":"https://insights.sbomify.com/CVE-2024-50684/"}