Upstream information

CVE-2025-27148 at MITRE

Description

Gradle is a build automation tool, and its native-platform tool provides Java bindings for native APIs. On Unix-like systems, the system temporary directory can be created with open permissions that allow multiple users to create and delete files within it. This library initialization could be vulnerable to a local privilege escalation from an attacker quickly deleting and recreating files in the system temporary directory. Gradle builds that rely on versions of net.rubygrapefruit:native-platform prior to 0.22-milestone-28 could be vulnerable to a local privilege escalation from an attacker quickly deleting and recreating files in the system temporary directory.

In net.rubygrapefruit:native-platform prior to version 0.22-milestone-28, if the `Native.get(Class<>)` method was called, without calling `Native.init(File)` first, with a non-`null` argument used as working file path, then the library would initialize itself using the system temporary directory and NativeLibraryLocator.java lines 68 through 78. Version 0.22-milestone-28 has been released with changes that fix the problem. Initialization is now mandatory and no longer uses the system temporary directory, unless such a path is passed for initialization. The only workaround for affected versions is to make sure to do a proper initialization, using a location that is safe.

Gradle 8.12, only that exact version, had codepaths where the initialization of the underlying native integration library took a default path, relying on copying the binaries to the system temporary directory. Any execution of Gradle exposed this exploit. Users of Windows or modern versions of macOS are not vulnerable, nor are users of a Unix-like operating system with the "sticky" bit set or `noexec` on their system temporary directory vulnerable. This problem was fixed in Gradle 8.12.1. Gradle 8.13 release also upgrades to a version of the native library that no longer has that bug. Some workarounds are available. On Unix-like operating systems, ensure that the "sticky" bit is set. This only allows the original user (or root) to delete a file. Mounting `/tmp` as `noexec` will prevent Gradle 8.12 from starting. Those who are are unable to change the permissions of the system temporary directory 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.

SUSE information

Overall state of this security issue: Resolved

This issue is currently rated as having important severity.

CVSS v3 Scores
  CNA (GitHub)
Base Score 8.8
Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Changed
Confidentiality Impact High
Integrity Impact High
Availability Impact High
CVSSv3 Version 3.1
SUSE Bugzilla entry: 1238060 [NEW]

No SUSE Security Announcements cross referenced.


Status of this issue by product and package

Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.

Product(s) Source package State
Products under general support and receiving all security fixes.
SUSE Linux Enterprise Desktop 15 SP6 gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP6 gradle Not affected
SUSE Linux Enterprise Module for Development Tools 15 SP6 gradle Not affected
SUSE Linux Enterprise Server 15 SP6 gradle Not affected
SUSE Linux Enterprise Server for SAP Applications 15 SP6 gradle Not affected
SUSE Manager Proxy 4.3 gradle Not affected
SUSE Manager Retail Branch Server 4.3 gradle Not affected
SUSE Manager Server 4.3 gradle Not affected
openSUSE Leap 15.6 gradle Not affected
Products under Long Term Service Pack support and receiving important and critical security fixes.
SUSE Linux Enterprise High Performance Computing 15 SP3 gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP3-ESPOS gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP4 gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP5 gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP5-ESPOS gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS gradle Not affected
SUSE Linux Enterprise Module for Development Tools 15 SP3 gradle Not affected
SUSE Linux Enterprise Module for Development Tools 15 SP4 gradle Not affected
SUSE Linux Enterprise Module for Development Tools 15 SP5 gradle Not affected
SUSE Linux Enterprise Server 15 SP3 gradle Not affected
SUSE Linux Enterprise Server 15 SP3-LTSS gradle Not affected
SUSE Linux Enterprise Server 15 SP4 gradle Not affected
SUSE Linux Enterprise Server 15 SP4-LTSS gradle Not affected
SUSE Linux Enterprise Server 15 SP5 gradle Not affected
SUSE Linux Enterprise Server 15 SP5-LTSS gradle Not affected
SUSE Linux Enterprise Server for SAP Applications 15 SP3 gradle Not affected
SUSE Linux Enterprise Server for SAP Applications 15 SP4 gradle Not affected
SUSE Linux Enterprise Server for SAP Applications 15 SP5 gradle Not affected
Products past their end of life and not receiving proactive updates anymore.
SUSE Enterprise Storage 7 gradle Not affected
SUSE Enterprise Storage 7.1 gradle Not affected
SUSE Linux Enterprise Desktop 15 SP2 gradle Not affected
SUSE Linux Enterprise Desktop 15 SP3 gradle Not affected
SUSE Linux Enterprise Desktop 15 SP4 gradle Not affected
SUSE Linux Enterprise Desktop 15 SP5 gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP2 gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP2-ESPOS gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP2-LTSS gradle Not affected
SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS gradle Not affected
SUSE Linux Enterprise Module for Development Tools 15 SP2 gradle Not affected
SUSE Linux Enterprise Real Time 15 SP2 gradle Not affected
SUSE Linux Enterprise Real Time 15 SP3 gradle Not affected
SUSE Linux Enterprise Real Time 15 SP4 gradle Not affected
SUSE Linux Enterprise Server 15 SP2 gradle Not affected
SUSE Linux Enterprise Server 15 SP2-BCL gradle Not affected
SUSE Linux Enterprise Server 15 SP2-LTSS gradle Not affected
SUSE Linux Enterprise Server 15 SP3-BCL gradle Not affected
SUSE Linux Enterprise Server for SAP Applications 15 SP2 gradle Not affected
SUSE Manager Proxy 4.1 gradle Not affected
SUSE Manager Proxy 4.2 gradle Not affected
SUSE Manager Retail Branch Server 4.1 gradle Not affected
SUSE Manager Retail Branch Server 4.2 gradle Not affected
SUSE Manager Server 4.1 gradle Not affected
SUSE Manager Server 4.2 gradle Not affected
openSUSE Leap 15.3 gradle Not affected
openSUSE Leap 15.4 gradle Not affected
openSUSE Leap 15.5 gradle Not affected


SUSE Timeline for this CVE

CVE page created: Wed Feb 26 00:00:56 2025
CVE page last modified: Fri Feb 28 12:12:25 2025