Artifact disclosure via inherited symlink permissions
Published Oct 5, 2023 · Updated Feb 13, 2025
Incorrect permission assignment in affected Gradle releases allows local users to expose files copied or archived through symbolic links. Copy and archive operations resolve each symbolic link to its target but assign the output the link's typically permissive mode rather than the target file's mode. Exploitation requires high-privileged local access and a symbolic link consumed by a build; the bounded result is unintended read access to resulting artifacts.
Summary
What happened
Incorrect permission assignment in affected Gradle releases allows local users to expose files copied or archived through symbolic links. Copy and archive operations resolve each symbolic link to its target but assign the output the link's typically permissive mode rather than the target file's mode. Exploitation requires high-privileged local access and a symbolic link consumed by a build; the bounded result is unintended read access to resulting artifacts.
The record
- CVE
- CVE-2023-44387
- Published
- Oct 5, 2023
- Updated
- Feb 13, 2025
- Vendor
- Gradle, Inc.
- Product
- Gradle Build Tool
- Classifications
- CWE-732
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Oct 5, 2023CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 7.6.0, < 7.6.3
- Affected versionversion=< 8.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo