Affected: Alpaquita:23: gradle, Alpaquita:stream: gradle

Affected: Bitnami: gradle

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.

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.

apache-ivy: XML External Entity vulnerability guava: insecure temporary directory creation JSON-java: parser confusion leads to OOM spring-boot: Security Bypass With Wildcard Pattern Matching on Cloud Foundry jose4j: Insecure iteration count setting bouncycastle: potential blind LDAP injection attack using a self-signed certificate jetty: Improper validation of HTTP/1 content-length tomcat: Open Redirect vulnerability in FORM authentication gradle: Possible local text file exfiltration by XML External entity injection gradle: Incorrect permission assignment for symlinked files used in copy or archiving operations zookeeper: Authorization Bypass in Apache ZooKeeper

Affected: Ubuntu:16.04:LTS: gradle, Ubuntu:Pro:18.04:LTS: gradle, Ubuntu:20.04:LTS: gradle, Ubuntu:22.04:LTS: gradle, Ubuntu:24.04:LTS: gradle, Ubuntu:25.10: gradle, Ubuntu:26.04:LTS: gradle

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.

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat JBoss A-MQ ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Informationen offenzulegen, Dateien zu manipulieren oder einen Denial of Service Zustand herbeizuführen.