{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25754 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25754 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25754 is a high-severity vulnerability in n/a, published on 16 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25754 and fix it if it is affected.\n\nWhat it is: CVE-2020-25754 is a high-severity vulnerability in n/a, published on 16 Jun 2021. 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-2020-25754 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-2020-25754/ (Markdown: https://insights.sbomify.com/CVE-2020-25754/index.md)","id":"CVE-2020-25754","markdown":"https://insights.sbomify.com/CVE-2020-25754/index.md","name":"CVE-2020-25754","record":{"aliases":["GHSA-cq4j-2685-h9rw"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Enphase Envoy device","requires_auth":"none","summary":"Attackers can bypass authentication on Enphase Envoy devices by deriving passwords from public serial numbers, leading to unauthorized access.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"envoy_firmware","vendor":"enphase"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"An issue was discovered on Enphase Envoy R3.x and D4.x devices. There is a custom PAM module for user authentication that circumvents traditional user authentication. This module uses a password derived from the MD5 hash of the username and serial number. The serial number can be retrieved by an unauthenticated user at /info.xml. Attempts to change the user password via passwd or other tools have no effect.","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-2020-25754","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2020-25755"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25753"},"products":["n/a"],"published":"2021-06-16","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25753","kev_date_added":null,"published":"2021-06-16"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2020-25755","kev_date_added":null,"published":"2021-06-16"},{"cvss_score":6.3,"headline":"Enphase Envoy OS Command Injection","id":"CVE-2023-33869","kev_date_added":null,"published":"2023-06-20"},{"cvss_score":5.3,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-25752","kev_date_added":null,"published":"2021-06-16"}],"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-04","vendors":["n/a"]},"summary":"Attackers can bypass authentication on Enphase Envoy devices by deriving passwords from public serial numbers, leading to unauthorized access.","url":"https://insights.sbomify.com/CVE-2020-25754/"}