First published: Thu Oct 05 2023(Updated: )
Gradle is a build tool with a focus on build automation and support for multi-language development. When copying or archiving symlinked files, Gradle resolves them but applies the permissions of the symlink itself instead of the permissions of the linked file to the resulting file. This leads to files having too much permissions given that symlinks usually are world readable and writeable. While it is unlikely this results in a direct vulnerability for the impacted build, it may open up attack vectors depending on where build artifacts end up being copied to or un-archived. In versions 7.6.3, 8.4 and above, Gradle will now properly use the permissions of the file pointed at by the symlink to set permissions of the copied or archived file.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Gradle Gradle | <7.6.3 | |
Gradle Gradle | >=8.0.0<8.4.0 | |
redhat/gradle | <7.6.3 | 7.6.3 |
redhat/gradle | <8.4 | 8.4 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Gradle is a build tool with a focus on build automation and support for multi-language development.
The vulnerability ID for Gradle is CVE-2023-44387.
The severity of CVE-2023-44387 is medium.
CVE-2023-44387 affects Gradle by resolving symlinked files but applying the permissions of the symlink itself instead of the linked file, potentially leading to incorrect file permissions.
To fix CVE-2023-44387, upgrade Gradle to version 7.6.4 or higher.