CVE and update status of the FreeBSD ports tree4,526 unaddressed CVEs in 616 portsAll times are CET

CVE details

CVE-2023-44387

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.

Score
3.2 low
Published
2023-10-05
Links
NVD · cve.org

Affected ports (4)

PortPackageVersionStatusMaintainer
devel/gradle5gradle55.0_3unaddressedyuri@FreeBSD.org
devel/gradle6gradle66.9.4_2unaddressedports@FreeBSD.org
devel/gradle62gradle626.2.2_3unaddressedyuri@FreeBSD.org
devel/gradle761gradle7617.6.1_2unaddressedports@FreeBSD.org

Template for a VuXML entry

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>gradle5</name>
	<range><lt>7.6.3</lt></range>
      </package>
      <package>
	<name>gradle6</name>
	<range><lt>7.6.3</lt></range>
      </package>
      <package>
	<name>gradle62</name>
	<range><lt>7.6.3</lt></range>
      </package>
      <package>
	<name>gradle761</name>
	<range><lt>7.6.3</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2023-44387</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2023-44387</url>
    </references>
    <dates>
      <discovery>2023-10-05</discovery>
      <entry>2026-10-25</entry>
    </dates>
  </vuln>