import UBI perl-Archive-Tar-2.38-6.el9_8.2

This commit is contained in:
AlmaLinux RelEng Bot 2026-08-02 23:38:04 -04:00
parent 3cb9bee984
commit 05a97f8568
2 changed files with 81 additions and 1 deletions

72
SOURCES/RHEL-191917.patch Normal file
View File

@ -0,0 +1,72 @@
From e1e4668a546f836356ebb75dfecddcc8c3cf2033 Mon Sep 17 00:00:00 2001
From: Stig Palmquist <stig@stig.io>
Date: Mon, 25 May 2026 19:11:34 +0100
Subject: [PATCH] Cpan entry size during read
Cap entry size during read to defend against attacker-controlled
size-field memory DoS
The tar header's 12-byte size field is attacker-controlled. Archive::Tar's
non-skip extract path at Tar.pm:501 allocates a Perl scalar of the declared
size before returning the read-short error, allowing a few-KB compressed
archive declaring a 100 GB inner entry to trigger immediate multi-GB
allocation. The existing $EXTRACT_BLOCK_SIZE is an output-side syswrite
chunk size, not an input cap.
Add $MAX_FILE_SIZE (default 1 GiB) checked once per entry, gating both the
chunked-skip and full-slurp branches. Set to 0 to disable the cap.
Signed-off-by: Chris 'BinGOs' Williams <chris@bingosnet.co.uk>
---
lib/Archive/Tar.pm | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/lib/Archive/Tar.pm b/lib/Archive/Tar.pm
index 7335d24..fe52677 100644
--- a/lib/Archive/Tar.pm
+++ b/lib/Archive/Tar.pm
@@ -24,6 +24,7 @@ use strict;
use vars qw[$DEBUG $error $VERSION $WARN $FOLLOW_SYMLINK $CHOWN $CHMOD
$DO_NOT_USE_PREFIX $HAS_PERLIO $HAS_IO_STRING $SAME_PERMISSIONS
$INSECURE_EXTRACT_MODE $ZERO_PAD_NUMBERS @ISA @EXPORT $RESOLVE_SYMLINK
+ $MAX_FILE_SIZE
];
@ISA = qw[Exporter];
@@ -39,6 +40,7 @@ $DO_NOT_USE_PREFIX = 0;
$INSECURE_EXTRACT_MODE = 0;
$ZERO_PAD_NUMBERS = 0;
$RESOLVE_SYMLINK = $ENV{'PERL5_AT_RESOLVE_SYMLINK'} || 'speed';
+$MAX_FILE_SIZE = 1024 * 1024 * 1024;
BEGIN {
use Config;
@@ -442,6 +444,14 @@ sub _read_tar {
my $block = BLOCK_SIZE->( $entry->size );
+ if ( $MAX_FILE_SIZE && $entry->size > $MAX_FILE_SIZE ) {
+ $self->_error( qq[Entry '] . $entry->full_path .
+ qq[' declared size ] . $entry->size .
+ qq[ bytes exceeds \$Archive::Tar::MAX_FILE_SIZE ] .
+ qq[($MAX_FILE_SIZE); refusing to allocate] );
+ next LOOP;
+ }
+
$data = $entry->get_content_by_ref;
my $skip = 0;
@@ -2194,6 +2204,13 @@ numbers. Added for compatibility with C<busybox> implementations.
It won't work for terminal, pipe or sockets or every non seekable source.
+=head2 $Archive::Tar::MAX_FILE_SIZE
+
+This variable holds an upper bound on the per-entry declared size that
+C<Archive::Tar> will accept when reading an archive. Entries whose header
+claims a larger size are refused with an error before any read allocation.
+Defaults to 1 GiB. Set to 0 to disable the cap.
+
=cut
=head1 FAQ

View File

@ -7,7 +7,7 @@
Name: perl-Archive-Tar
Version: 2.38
Release: 6%{?dist}.1
Release: 6%{?dist}.2
Summary: A module for Perl manipulation of .tar files
License: GPL+ or Artistic
URL: https://metacpan.org/release/Archive-Tar
@ -17,6 +17,8 @@ Patch0: Archive-Tar-2.02-Do-not-sleep-in-Makefile.PL.patch
# https://github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158
# https://github.com/jib/archive-tar-new/commit/484f71ea0189ed46690f50dc7ee71d4b8bc0e70f
Patch1: RHEL-181662.patch
# https://github.com/jib/archive-tar-new/commit/f9af01426038e29d9578825a0cd3626946ab08c7
Patch2: RHEL-191917.patch
BuildArch: noarch
# Most of the BRS are needed only for tests, compression support at run-time
# is optional soft dependency.
@ -101,6 +103,7 @@ will also support compressed or gzipped tar files.
%setup -q -n Archive-Tar-%{version}
%patch0 -p1 -b .orig
%patch1 -p1
%patch2 -p1
%build
perl Makefile.PL INSTALLDIRS=vendor NO_PACKLIST=1 NO_PERLLOCAL=1
@ -122,6 +125,11 @@ make test
%changelog
* Fri Jul 03 2026 RHEL Packaging Agent <redhat-ymir-agent@redhat.com> - 2.38-6.2
- Fix CVE-2026-9538: add $MAX_FILE_SIZE cap for tar entry size during
read to prevent memory allocation DoS
- Resolves: RHEL-191917
* Fri Jun 05 2026 RHEL Packaging Agent <redhat-ymir-agent@redhat.com> - 2.38-6.1
- Fix CVE-2026-42496: validate symlink and hardlink targets in secure
extract mode