Threats tagged 'bitnami'

Pillow is a Python imaging library. From 5.2.0 until 12.3.0, Pillow's TGA RLE encoder reads past its packed row buffer when saving a mode 1 image with TGA RLE compression, allowing adjacent process heap bytes to be copied into the generated TGA file. This issue is fixed in version 12.3.0.

A high-severity vulnerability (CVE-2026-59205) exists in the Python Pillow imaging library prior to version 12.3.0. The issue involves an out-of-bounds write in the ImageCms.ImageCmsTransform.apply(im, imOut) API, which can cause controlled native heap corruption if the output image mode does not match the transform's declared output mode. This vulnerability has a CVSS score of 7.5 and is fixed in Pillow version 12.3.0.

Pillow is a Python imaging library. From 12.0.0 through 12.2.0, Pillow's EPS parser in PIL/EpsImagePlugin.py accepts a negative byte count in the %%BeginBinary directive, allowing a crafted EPS file to cause Image.open() to seek backwards to the same directive and parse it repeatedly in an infinite loop. This issue is fixed in version 12.3.0.

Pillow is a Python imaging library. Prior to 12.3.0, Pillow public image coordinate APIs can trigger a native heap out-of-bounds write when given coordinates near the signed 32-bit integer limits in Image.paste(), Image.crop(), or Image.alpha_composite(). This issue is fixed in version 12.3.0.

Pillow is a Python imaging library. From 8.2.0 through 12.2.0, src/libImaging/Jpeg2KDecode.c accumulates total_component_width across every tile in a JPEG2000 image instead of recomputing it per tile, allowing a crafted tiled JPEG2000 file to force substantially higher transient memory usage and trigger out-of-memory failures during decoding. This issue is fixed in version 12.3.0.

Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 contain a vulnerability where hidden post revisions can be leaked through visible diffs on adjacent revisions. This occurs due to the PostRevisionSerializer exposing information that should remain hidden from regular users. The issue has been fixed in the specified versions.

Discourse, an open-source discussion platform, contains a remote code execution vulnerability related to processing PDF uploads under certain non-default configurations. This vulnerability affects versions prior to 2026.1.5, 2026.4.2, and 2026.5.1 and is patched in these versions. The issue allows an attacker to execute code on the server by exploiting the PDF upload processing. No known exploits in the wild have been reported. The vulnerability is rated as high severity.

Cilium is a networking, observability, and security solution. Prior to 1.17.16, from 1.18.2 to 1.18.9, and from 1.19.0 to 1.19.3, users with the ability to create CiliumLocalRedirectPolicies can specify arbitrary ClusterIPs via addressMatcher, enabling hijacking traffic to Services in any namespace and bypassing namespace scoping enforced by serviceMatcher; deleting such a policy can also corrupt Cilium internal service state and stop service translation for the affected Service. This issue is fixed in versions 1.17.16, 1.18.10, and 1.19.4.

Composer versions prior to 2.2.29 and 2.10.2 are vulnerable to an arbitrary file write issue. A malicious package from an untrusted repository can exploit improper validation of package names to write files outside the vendor directory and project during install or update. This vulnerability is fixed in Composer versions 2.2.29 and 2.10.2.

Composer versions prior to 2.2.29 and 2.10.2 may leak HTTP Basic authentication credentials embedded in URLs to verbose debug logs when run with -vvv verbosity. This includes sensitive tokens such as GitHub Personal Access Tokens in the username portion of repository or package URLs. The issue arises because certain components did not sanitize username-only credentials in URLs before logging. Fixed versions 2.2.29 and 2.10.2 address this by properly sanitizing such credentials in debug output.

Composer versions prior to 2.2.29 and 2.10.2 contain a path traversal vulnerability in the package bin field. This flaw allows a package's bin entry with '..' path segments to escape the intended install directory, causing Composer to chmod arbitrary existing host files to world-readable and world-executable during install, update, or require operations. The issue is fixed in versions 2.2.29 and 2.10.2.

Insufficient Technical Documentation vulnerability in Apache Tomcat since the requirements to securely configure the EncryptInterceptor were not clearly documented. This issue affects Apache Tomcat: from 11.0.0-M1 through 11.0.23, from 10.1.0-M1 through 10.1.56, from 9.0.13 through 9.0.119, from 8.5.38 through 8.5.100, from 7.0.100 through 7.0.109. Other versions that have reached end of support may also be affected. Users are recommended to upgrade to version 11.0.24, 10.1.57 or 9.0.120 which fix the issue.

A missing authorization vulnerability in GitLab EE versions 18.9 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 could allow an authenticated user with minimal access permissions to read work item metadata from private projects. This issue has been remediated in the specified fixed versions.

A missing authorization vulnerability in GitLab CE/EE allows unauthenticated users to determine the existence of private projects under certain conditions. This issue affects versions from 9.1 up to but not including 18.11.7, 19.0 up to but not including 19.0.4, and 19.1 up to but not including 19.1.2. The vulnerability arises from improper authorization controls on cross-project reference pages. A fix is available for the affected versions.

A cross-site scripting (XSS) vulnerability was discovered in GitLab Enterprise Edition affecting multiple versions from 13.11 up to but not including 18.11.7, 19.0 up to but not including 19.0.4, and 19.1 up to but not including 19.1.2. This vulnerability could allow an authenticated user with developer-role permissions to execute arbitrary scripts in another user's browser session due to improper sanitization of user input. The issue has been remediated in the specified fixed versions.

GitLab EE versions from 18.2 up to but not including 18.11.7, 19.0 up to but not including 19.0.4, and 19.1 up to but not including 19.1.2 contain an authorization vulnerability. Under certain conditions, an authenticated user with auditor-level access could improperly modify compliance violation records due to incorrect authorization on specific GraphQL operations. This issue has been remediated in the fixed versions.

A cross-site scripting (XSS) vulnerability in GitLab CE/EE allows authenticated users to execute arbitrary scripts in other users' browser sessions due to improper sanitization of user input. This affects versions from 15.7 up to but not including 18.11.7, 19.0 up to but not including 19.0.4, and 19.1 up to but not including 19.1.2. The issue has been remediated in the stated fixed versions.

A vulnerability in GitLab EE versions from 9.5 up to but not including 18.11.7, 19.0 up to 19.0.4, and 19.1 up to 19.1.2 allows an authenticated user with maintainer-role permissions to access another user's stored credentials due to insufficient authorization controls. This issue has been remediated in the specified fixed versions.

A vulnerability in GitLab CE/EE versions from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 allows an authenticated user to create a repository where the content shown in the web interface differs from the content available for download. This is due to improper handling of Git reference name resolution.

This update includes the following RPMs: tomcat10: * tomcat10-10.1.57-1.hum1 (noarch) * tomcat10-admin-webapps-10.1.57-1.hum1 (noarch) * tomcat10-common-10.1.57-1.hum1 (noarch) * tomcat10-docs-webapp-10.1.57-1.hum1 (noarch) * tomcat10-el-5.0-api-10.1.57-1.hum1 (noarch) * tomcat10-jsp-3.1-api-10.1.57-1.hum1 (noarch) * tomcat10-lib-10.1.57-1.hum1 (noarch) * tomcat10-servlet-6.0-api-10.1.57-1.hum1 (noarch) * tomcat10-user-instance-10.1.57-1.hum1 (noarch) * tomcat10-webapps-10.1.57-1.hum1 (noarch) * tomcat10-10.1.57-1.hum1.src (src)