Docker buildpack-deps:bullseye-curl

Vulnerabilities

39 via 63 paths

Dependencies

135

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:unstable
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 2
  • 1
  • 36
Status
  • 39
  • 0
  • 0

high severity

Out-of-bounds Read

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.34.0-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* sqlite3/libsqlite3-0@3.34.0-1

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read. An out-of-bounds read was addressed with improved bounds checking. This issue is fixed in iOS 13.5 and iPadOS 13.5, macOS Catalina 10.15.5, tvOS 13.4.5, watchOS 6.2.5, iTunes 12.10.7 for Windows, iCloud for Windows 11.2, iCloud for Windows 7.19. A malicious application may cause a denial of service or potentially disclose memory contents.

Remediation

There is no fixed version for sqlite3.

References

high severity

Information Exposure

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.2-4 and systemd/libudev1@247.2-4

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* systemd/libsystemd0@247.2-4
  • Introduced through: buildpack-deps:bullseye-curl@* systemd/libudev1@247.2-4

Overview

systemd 242 changes the VT1 mode upon a logout, which allows attackers to read cleartext passwords in certain circumstances, such as watching a shutdown, or using Ctrl-Alt-F1 and Ctrl-Alt-F2. This occurs because the KDGKBMODE (aka current keyboard mode) check is mishandled.

References

medium severity

Cryptographic Issues

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.7-2

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* libgcrypt20@1.8.7-2

Overview

In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.)

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@2.1.15 and apt/libapt-pkg6.0@2.1.15

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* apt@2.1.15
  • Introduced through: buildpack-deps:bullseye-curl@* apt/libapt-pkg6.0@2.1.15

Overview

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils/coreutils
  • Introduced through: coreutils/coreutils@8.32-4+b1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* coreutils/coreutils@8.32-4+b1

Overview

chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.

References

low severity

Race Condition

  • Vulnerable module: coreutils/coreutils
  • Introduced through: coreutils/coreutils@8.32-4+b1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* coreutils/coreutils@8.32-4+b1

Overview

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

References

low severity

Access Restriction Bypass

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

** DISPUTED ** GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat."

References

low severity

CVE-2010-4051

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

The regcomp implementation in the GNU C Library (aka glibc or libc6) through 2.11.3, and 2.12.x through 2.12.2, allows context-dependent attackers to cause a denial of service (application crash) via a regular expression containing adjacent bounded repetitions that bypass the intended RE_DUP_MAX limitation, as demonstrated by a {10,}{10,}{10,}{10,}{10,} sequence in the proftpd.gnu.c exploit for ProFTPD, related to a "RE_DUP_MAX overflow."

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

** DISPUTED ** GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat."

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

** DISPUTED ** GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat."

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

Stack consumption vulnerability in the regcomp implementation in the GNU C Library (aka glibc or libc6) through 2.11.3, and 2.12.x through 2.12.2, allows context-dependent attackers to cause a denial of service (resource exhaustion) via a regular expression containing adjacent repetition operators, as demonstrated by a {10,}{10,}{10,}{10,} sequence in the proftpd.gnu.c exploit for ProFTPD.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

** DISPUTED ** In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-9 and glibc/libc6@2.31-9

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc-bin@2.31-9
  • Introduced through: buildpack-deps:bullseye-curl@* glibc/libc6@2.31-9

Overview

** DISPUTED ** GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability."

References

low severity

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.0-5

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* gnutls28/libgnutls30@3.7.0-5

Overview

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

References

low severity

Improper Input Validation

  • Vulnerable module: iptables/libxtables12
  • Introduced through: iptables/libxtables12@1.8.6-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* iptables/libxtables12@1.8.6-1

Overview

extensions/libxt_tcp.c in iptables through 1.4.21 does not match TCP SYN+FIN packets in --syn rules, which might allow remote attackers to bypass intended firewall restrictions via crafted packets. NOTE: the CVE-2012-6638 fix makes this issue less relevant.

References

low severity

CVE-2004-0971

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-4, krb5/libk5crypto3@1.18.3-4 and others

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libgssapi-krb5-2@1.18.3-4
  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libk5crypto3@1.18.3-4
  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libkrb5-3@1.18.3-4
  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libkrb5support0@1.18.3-4

Overview

The krb5-send-pr script in the kerberos5 (krb5) package in Trustix Secure Linux 1.5 through 2.1, and possibly other operating systems, allows local users to overwrite files via a symlink attack on temporary files.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.18.3-4, krb5/libk5crypto3@1.18.3-4 and others

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libgssapi-krb5-2@1.18.3-4
  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libk5crypto3@1.18.3-4
  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libkrb5-3@1.18.3-4
  • Introduced through: buildpack-deps:bullseye-curl@* krb5/libkrb5support0@1.18.3-4

Overview

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.7-2

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* libgcrypt20@1.8.7-2

Overview

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

References

low severity

Cryptographic Issues

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.56+dfsg-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* openldap/libldap-2.4-2@2.4.56+dfsg-1

Overview

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

References

low severity

Improper Certificate Validation

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.56+dfsg-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* openldap/libldap-2.4-2@2.4.56+dfsg-1

Overview

Affected versions of this package are vulnerable to Improper Certificate Validation libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

Remediation

There is no fixed version for openldap.

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.56+dfsg-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* openldap/libldap-2.4-2@2.4.56+dfsg-1

Overview

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

References

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.56+dfsg-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* openldap/libldap-2.4-2@2.4.56+dfsg-1

Overview

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1i-1 and openssl/libssl1.1@1.1.1i-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* openssl@1.1.1i-1
  • Introduced through: buildpack-deps:bullseye-curl@* openssl/libssl1.1@1.1.1i-1

Overview

The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE.

References

low severity

Cryptographic Issues

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1i-1 and openssl/libssl1.1@1.1.1i-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* openssl@1.1.1i-1
  • Introduced through: buildpack-deps:bullseye-curl@* openssl/libssl1.1@1.1.1i-1

Overview

OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack."

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* pcre3/libpcre3@2:8.39-13

Overview

Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 4) or possibly have unspecified other impact via a crafted file.

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* pcre3/libpcre3@2:8.39-13

Overview

Stack-based buffer overflow in the pcre32_copy_substring function in pcre_get.c in libpcre1 in PCRE 8.40 allows remote attackers to cause a denial of service (WRITE of size 268) or possibly have unspecified other impact via a crafted file.

References

low severity

Out-of-Bounds

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* pcre3/libpcre3@2:8.39-13

Overview

** DISPUTED ** In PCRE 8.41, after compiling, a pcretest load test PoC produces a crash overflow in the function match() in pcre_exec.c because of a self-recursive call. NOTE: third parties dispute the relevance of this report, noting that there are options that can be used to limit the amount of stack that is used.

References

low severity

Out-of-bounds Read

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* pcre3/libpcre3@2:8.39-13

Overview

Affected versions of this package are vulnerable to Out-of-bounds Read libpcre in PCRE before 8.43 allows a subject buffer over-read in JIT when UTF is disabled, and \X or \R has more than one fixed quantifier, a related issue to CVE-2019-20454.

Remediation

There is no fixed version for pcre3.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-13

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* pcre3/libpcre3@2:8.39-13

Overview

In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.

References

low severity

Link Following

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.32.0-6

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* perl/perl-base@5.32.0-6

Overview

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

References

low severity

Access Restriction Bypass

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps:bullseye-curl@* shadow/passwd@1:4.8.1-1

Overview

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

References

low severity

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps:bullseye-curl@* shadow/passwd@1:4.8.1-1

Overview

shadow 4.8, in certain circumstances affecting at least Gentoo, Arch Linux, and Void Linux, allows local users to obtain root access because setuid programs are misconfigured. Specifically, this affects shadow 4.8 when compiled using --with-libpam but without explicitly passing --disable-account-tools-setuid, and without a PAM configuration suitable for use with setuid account management tools. This combination leads to account management tools (groupadd, groupdel, groupmod, useradd, userdel, usermod) that can easily be used by unprivileged local users to escalate privileges to root in multiple ways. This issue became much more relevant in approximately December 2019 when an unrelated bug was fixed (i.e., the chmod calls to suidusbins were fixed in the upstream Makefile which is now included in the release version 4.8).

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1 and shadow/passwd@1:4.8.1-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* shadow/login@1:4.8.1-1
  • Introduced through: buildpack-deps:bullseye-curl@* shadow/passwd@1:4.8.1-1

Overview

shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees

References

low severity

CVE-2019-9619

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.2-4 and systemd/libudev1@247.2-4

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* systemd/libsystemd0@247.2-4
  • Introduced through: buildpack-deps:bullseye-curl@* systemd/libudev1@247.2-4

Overview

CVE-2019-9619

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@247.2-4 and systemd/libudev1@247.2-4

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* systemd/libsystemd0@247.2-4
  • Introduced through: buildpack-deps:bullseye-curl@* systemd/libudev1@247.2-4

Overview

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

References

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.32+dfsg-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* tar@1.32+dfsg-1

Overview

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

This is considered intended behaviour, as tar is an archiving tool and one needs to give -p as a command line flag

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tar
  • Introduced through: tar@1.32+dfsg-1

Detailed paths

  • Introduced through: buildpack-deps:bullseye-curl@* tar@1.32+dfsg-1

Overview

pax_decode_header in sparse.c in GNU Tar before 1.32 had a NULL pointer dereference when parsing certain archives that have malformed extended headers.

References