Threats Tagged 'cve-2026-39245'

This update includes the following RPMs: dotnet8.0: * aspnetcore-runtime-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * aspnetcore-runtime-dbg-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * aspnetcore-targeting-pack-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * dotnet-apphost-pack-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * dotnet-hostfxr-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * dotnet-runtime-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * dotnet-runtime-dbg-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * dotnet-sdk-8.0-8.0.128-1.1.hum1 (aarch64, x86_64) * dotnet-sdk-8.0-source-built-artifacts-8.0.128-1.1.hum1 (aarch64, x86_64) * dotnet-sdk-dbg-8.0-8.0.128-1.1.hum1 (aarch64, x86_64) * dotnet-targeting-pack-8.0-8.0.28-1.1.hum1 (aarch64, x86_64) * dotnet-templates-8.0-8.0.128-1.1.hum1 (aarch64, x86_64) * dotnet8.0-8.0.128-1.1.hum1.src (src) Security Fix(es): dotnet8.0: * CVE-2026-59725 * CVE-2026-59869

decompress before 4.2.2 contains an improper path containment check that enables directory traversal and arbitrary file write. The safeMakeDir function (index.js line 29) and the extraction path validation (index.js line 106) use String.indexOf() to verify the resolved path is within the output directory: realDestinationDir.indexOf(realOutputPath) !== 0. This check is flawed because it does not enforce a path separator boundary. For example, "/tmp/app_config".indexOf("/tmp/app") returns 0, incorrectly passing the check even though /tmp/app_config is outside /tmp/app. Combined with the unvalidated symlink creation in the same package, an attacker can write arbitrary files to directories adjacent to the extraction target. This is a bypass of the fix for CVE-2020-12265. The correct check requires appending a path separator: realParentPath.indexOf(realOutputPath + path.sep) !== 0.