Incorrect Permission Assignment for Critical Resource Affecting rh-maven36-byte-buddy-parent package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.05% (20th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-RHMAVEN36BYTEBUDDYPARENT-5952487
  • published10 Oct 2023
  • disclosed5 Oct 2023

Introduced: 5 Oct 2023

CVE-2023-44387  (opens in a new tab)
CWE-732  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 rh-maven36-byte-buddy-parent.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rh-maven36-byte-buddy-parent package and not the rh-maven36-byte-buddy-parent package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

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.

CVSS Scores

version 3.1