Bug 1216039 (CVE-2023-44387) - VUL-0: CVE-2023-44387: gradle: 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
Summary: VUL-0: CVE-2023-44387: gradle: When copying or archiving symlinked files, Gra...
Status: NEW
Alias: CVE-2023-44387
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Minor
Target Milestone: ---
Assignee: Gus Kenion
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/380944/
Whiteboard: CVSSv3.1:SUSE:CVE-2023-44387:3.2:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-10-09 07:39 UTC by SMASH SMASH
Modified: 2024-01-17 07:41 UTC (History)
3 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
stoyan.manolov: needinfo? (gus.kenion)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2023-10-09 07:39:34 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-44387