{"answers":{"affected":"1 open source package ship an affected version, including gradle. It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-29429 in the wild and no public exploit code.","fix":"Upgrade gradle to 7.0.0 or later.","what":"CVE-2021-29429 is a medium-severity vulnerability in gradle, published on 12 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-29429 and fix it if it is affected.\n\nWhat it is: CVE-2021-29429 is a medium-severity vulnerability in gradle, published on 12 Apr 2021. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-29429 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gradle (Bitnami): affected all versions; fixed in 7.0.0\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-29429/ (Markdown: https://insights.sbomify.com/CVE-2021-29429/index.md)","id":"CVE-2021-29429","markdown":"https://insights.sbomify.com/CVE-2021-29429/index.md","name":"CVE-2021-29429","record":{"aliases":["BIT-gradle-2021-29429","DEBIAN-CVE-2021-29429","GHSA-fp8h-qmr5-j4c8"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Gradle build tool","requires_auth":"none","summary":"Local attackers can read sensitive files downloaded by Gradle due to insecure temporary directory permissions, exposing data to other users on the system.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"gradle","vendor":"gradle"},{"product":"quarkus","vendor":"quarkus"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-377","name":"DEPRECATED: Insecure Temporary File"}],"description":"In Gradle before version 7.0, files created with open permissions in the system temporary directory can allow an attacker to access information downloaded by Gradle. Some builds could be vulnerable to a local information disclosure. Remote files accessed through TextResourceFactory are downloaded into the system temporary directory first. Sensitive information contained in these files can be exposed to other local users on the same system. If you do not use the `TextResourceFactory` API, you are not vulnerable. As of Gradle 7.0, uses of the system temporary directory have been moved to the Gradle User Home directory. By default, this directory is restricted to the user running the build. As a workaround, set a more restrictive umask that removes read access to other users. When files are created in the system temporary directory, they will not be accessible to other users. If you are unable to change your system's umask, you can move the Java temporary directory by setting the System Property `java.io.tmpdir`. The new path needs to limit permissions to the build user only.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure through temporary directory permissions","id":"CVE-2021-29429","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":1,"n_references":2,"next":{"headline":"Denial of service attack via memory exhaustion","id":"CVE-2021-29430"},"packages":[{"ecosystem":"Bitnami","fixed":["7.0.0"],"introduced":["0"],"last_affected":[],"package":"gradle","purl":"pkg:bitnami/gradle","source":"BIT-gradle-2021-29429"}],"prev":{"headline":"Local privilege escalation through system temporary directory","id":"CVE-2021-29428"},"products":["gradle"],"published":"2021-04-12","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-15052","kev_date_added":null,"published":"2019-08-14"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-6199","kev_date_added":null,"published":"2017-02-07"},{"cvss_score":8.8,"headline":"Local privilege escalation through system temporary directory","id":"CVE-2021-29428","kev_date_added":null,"published":"2021-04-13"},{"cvss_score":8.6,"headline":"Gradle fails to disable repositories which can expose builds to malicious artifacts","id":"CVE-2026-22816","kev_date_added":null,"published":"2026-01-16"},{"cvss_score":8.6,"headline":"Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts","id":"CVE-2026-22865","kev_date_added":null,"published":"2026-01-16"},{"cvss_score":8.1,"headline":"Deserialization in n/a","id":"CVE-2021-41588","kev_date_added":null,"published":"2021-09-24"},{"cvss_score":8,"headline":"Repository content filters do not work in Settings pluginManagement","id":"CVE-2021-29427","kev_date_added":null,"published":"2021-04-13"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"2026-10-08","vendors":["gradle"]},"summary":"Local attackers can read sensitive files downloaded by Gradle due to insecure temporary directory permissions, exposing data to other users on the system.","url":"https://insights.sbomify.com/CVE-2021-29429/"}