{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-36224 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-36224 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-36224 is a critical vulnerability in n/a, published on 6 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-36224 and fix it if it is affected.\n\nWhat it is: CVE-2021-36224 is a critical vulnerability in n/a, published on 6 Feb 2023. 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-2021-36224 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-2021-36224/ (Markdown: https://insights.sbomify.com/CVE-2021-36224/index.md)","id":"CVE-2021-36224","markdown":"https://insights.sbomify.com/CVE-2021-36224/index.md","name":"CVE-2021-36224","record":{"aliases":["GHSA-hj2g-q4fc-38mp"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Western Digital My Cloud","requires_auth":"none","summary":"Attackers can gain unauthorized access to Western Digital My Cloud devices using a default nobody account with a blank password.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"my_cloud_os","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-798","name":"Use of Hard-coded Credentials"}],"description":"Western Digital My Cloud devices before OS5 have a nobody account with a blank password.","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-2021-36224","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2021-36225"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2021-36222"},"products":["n/a"],"published":"2023-02-06","related":[{"cvss_score":10,"headline":"Authentication Bypass issue in My Cloud OS 5 devices","id":"CVE-2023-22814","kev_date_added":null,"published":"2023-06-30"},{"cvss_score":9.8,"headline":"Command Injection Vulnerability in Western Digital My Cloud devices","id":"CVE-2022-29842","kev_date_added":null,"published":"2023-05-10"},{"cvss_score":9.8,"headline":"Security feature bypass in n/a","id":"CVE-2021-36226","kev_date_added":null,"published":"2023-02-06"},{"cvss_score":9.8,"headline":"Pre-authenticated stack overflow vulnerability on FTP Service","id":"CVE-2022-22989","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2021-36225","kev_date_added":null,"published":"2023-02-06"},{"cvss_score":8.8,"headline":"Insufficient Verification of Data Authenticity Remote Code Execution Vulnerability on Western Digital My Cloud devices.","id":"CVE-2022-22994","kev_date_added":null,"published":"2022-01-28"}],"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 gain unauthorized access to Western Digital My Cloud devices using a default nobody account with a blank password.","url":"https://insights.sbomify.com/CVE-2021-36224/"}