{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25765 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-25765 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-25765 is a critical command injection vulnerability in n/a, published on 27 Oct 2020. 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-25765 and fix it if it is affected.\n\nWhat it is: CVE-2020-25765 is a critical command injection vulnerability in n/a, published on 27 Oct 2020. 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-25765 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-25765/ (Markdown: https://insights.sbomify.com/CVE-2020-25765/index.md)","id":"CVE-2020-25765","markdown":"https://insights.sbomify.com/CVE-2020-25765/index.md","name":"CVE-2020-25765","record":{"aliases":["GHSA-3m38-3rh9-4x65"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Western Digital My Cloud","requires_auth":"none","summary":"Remote attackers can execute arbitrary code on Western Digital My Cloud devices via insufficient input validation in reg_device.php.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"my_cloud_firmware","vendor":"westerndigital"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Addressed remote code execution vulnerability in reg_device.php due to insufficient validation of user input.in Western Digital My Cloud Devices prior to 5.4.1140.","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":"Command injection in n/a","id":"CVE-2020-25765","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2020-25766"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2020-25763"},"products":["n/a"],"published":"2020-10-27","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-27744","kev_date_added":null,"published":"2020-10-29"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-12830","kev_date_added":null,"published":"2020-10-27"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-27158","kev_date_added":null,"published":"2020-10-27"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2020-27159","kev_date_added":null,"published":"2020-10-27"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-27160","kev_date_added":null,"published":"2020-10-27"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-9148","kev_date_added":null,"published":"2018-03-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-04","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary code on Western Digital My Cloud devices via insufficient input validation in reg_device.php.","url":"https://insights.sbomify.com/CVE-2020-25765/"}