{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-41589 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41589 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41589 is a critical missing authorization vulnerability in n/a, published on 27 Oct 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-2021-41589 and fix it if it is affected.\n\nWhat it is: CVE-2021-41589 is a critical missing authorization vulnerability in n/a, published on 27 Oct 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-2021-41589 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-41589/ (Markdown: https://insights.sbomify.com/CVE-2021-41589/index.md)","id":"CVE-2021-41589","markdown":"https://insights.sbomify.com/CVE-2021-41589/index.md","name":"CVE-2021-41589","record":{"aliases":["GHSA-65w8-859v-42ph"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Gradle Enterprise Build Cache","requires_auth":"none","summary":"Attackers can poison the build cache and execute malicious code due to default anonymous write access in Gradle Enterprise Build Cache Node.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"build_cache_node","vendor":"gradle"},{"product":"enterprise","vendor":"gradle"}],"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-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"In Gradle Enterprise before 2021.3 (and Enterprise Build Cache Node before 10.0), there is potential cache poisoning and remote code execution when running the build cache node with its default configuration. This configuration allows anonymous access to the configuration user interface and anonymous write access to the build cache. If access control to the build cache is not changed from the default open configuration, a malicious actor with network access can populate the cache with manipulated entries that may execute malicious code as part of a build process. This applies to the build cache provided with Gradle Enterprise and the separate build cache node service if used. If access control to the user interface is not changed from the default open configuration, a malicious actor can undo build cache access control in order to populate the cache with manipulated entries that may execute malicious code as part of a build process. This does not apply to the build cache provided with Gradle Enterprise, but does apply to the separate build cache node service if used.","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":"Missing authorization in n/a","id":"CVE-2021-41589","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Server-side request forgery in n/a","id":"CVE-2021-41590"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2021-41588"},"products":["n/a"],"published":"2021-10-27","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-11403","kev_date_added":null,"published":"2019-04-21"}],"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 poison the build cache and execute malicious code due to default anonymous write access in Gradle Enterprise Build Cache Node.","url":"https://insights.sbomify.com/CVE-2021-41589/"}