Docker buildpack-deps:19.04-scm

Vulnerabilities

43 via 111 paths

Dependencies

173

Source

Group 6 Copy Created with Sketch. Docker

Target OS

ubuntu:19.04
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 10
  • 33
Status
  • 43
  • 0
  • 0

medium severity

Out-of-bounds Write

  • Vulnerable module: e2fsprogs
  • Introduced through: e2fsprogs@1.44.6-1ubuntu0.1, e2fsprogs/libcom-err2@1.44.6-1ubuntu0.1 and others
  • Fixed in: 1.44.6-1ubuntu0.2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* e2fsprogs@1.44.6-1ubuntu0.1
  • Introduced through: buildpack-deps:19.04-scm@* e2fsprogs/libcom-err2@1.44.6-1ubuntu0.1
  • Introduced through: buildpack-deps:19.04-scm@* e2fsprogs/libext2fs2@1.44.6-1ubuntu0.1
  • Introduced through: buildpack-deps:19.04-scm@* e2fsprogs/libss2@1.44.6-1ubuntu0.1

Overview

A code execution vulnerability exists in the directory rehashing functionality of E2fsprogs e2fsck 1.45.4. A specially crafted ext4 directory can cause an out-of-bounds write on the stack, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability.

References

medium severity

Reachable Assertion

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

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* krb5/libgssapi-krb5-2@1.17-1
  • Introduced through: buildpack-deps:19.04-scm@* krb5/libk5crypto3@1.17-1
  • Introduced through: buildpack-deps:19.04-scm@* krb5/libkrb5-3@1.17-1
  • Introduced through: buildpack-deps:19.04-scm@* krb5/libkrb5support0@1.17-1

Overview

A Reachable Assertion issue was discovered in the KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), the attacker can crash the KDC by making an S4U2Self request.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libbsd/libbsd0
  • Introduced through: libbsd/libbsd0@0.9.1-2
  • Fixed in: 0.9.1-2ubuntu0.1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* libbsd/libbsd0@0.9.1-2

Overview

nlist.c in libbsd before 0.10.0 has an out-of-bounds read during a comparison for a symbol name from the string table (strtab).

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.36.0-2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* nghttp2/libnghttp2-14@1.36.0-2

Overview

Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

References

medium severity

Resource Exhaustion

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.36.0-2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* nghttp2/libnghttp2-14@1.36.0-2

Overview

Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.

References

medium severity

Arbitrary Code Injection

  • Vulnerable module: python2.7
  • Introduced through: python2.7@2.7.16-2ubuntu0.2, python2.7/libpython2.7-minimal@2.7.16-2ubuntu0.2 and others

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* python2.7@2.7.16-2ubuntu0.2
  • Introduced through: buildpack-deps:19.04-scm@* python2.7/libpython2.7-minimal@2.7.16-2ubuntu0.2
  • Introduced through: buildpack-deps:19.04-scm@* python2.7/libpython2.7-stdlib@2.7.16-2ubuntu0.2
  • Introduced through: buildpack-deps:19.04-scm@* python2.7/python2.7-minimal@2.7.16-2ubuntu0.2

Overview

An issue was discovered in urllib2 in Python 2.x through 2.7.17 and urllib in Python 3.x through 3.8.0. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the host component of a URL) followed by an HTTP header. This is similar to the CVE-2019-9740 query string issue and the CVE-2019-9947 path string issue. (This is not exploitable when glibc has CVE-2016-10739 fixed.). This is fixed in: v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1; v3.6.11, v3.6.11rc1, v3.6.12; v3.7.8, v3.7.8rc1, v3.7.9; v3.8.3, v3.8.3rc1, v3.8.4, v3.8.4rc1, v3.8.5, v3.8.6, v3.8.6rc1.

References

medium severity

Access of Uninitialized Pointer

  • Vulnerable module: subversion
  • Introduced through: subversion@1.10.0-2ubuntu3 and subversion/libsvn1@1.10.0-2ubuntu3

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* subversion@1.10.0-2ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* subversion/libsvn1@1.10.0-2ubuntu3

Overview

Subversion's mod_dav_svn Apache HTTPD module versions 1.11.0 and 1.10.0 to 1.10.3 will crash after dereferencing an uninitialized pointer if the client omits the root path in a recursive directory listing operation.

References

medium severity

Improper Input Validation

  • Vulnerable module: subversion
  • Introduced through: subversion@1.10.0-2ubuntu3 and subversion/libsvn1@1.10.0-2ubuntu3

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* subversion@1.10.0-2ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* subversion/libsvn1@1.10.0-2ubuntu3

Overview

In Apache Subversion versions up to and including 1.9.10, 1.10.4, 1.12.0, Subversion's svnserve server process may exit when a client sends certain sequences of protocol commands. This can lead to disruption for users of the server.

References

medium severity

Improper Input Validation

  • Vulnerable module: subversion
  • Introduced through: subversion@1.10.0-2ubuntu3 and subversion/libsvn1@1.10.0-2ubuntu3

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* subversion@1.10.0-2ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* subversion/libsvn1@1.10.0-2ubuntu3

Overview

In Apache Subversion versions up to and including 1.9.10, 1.10.4, 1.12.0, Subversion's svnserve server process may exit when a well-formed read-only request produces a particular answer. This can lead to disruption for users of the server.

References

medium severity

Information Exposure

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@240-6ubuntu5.8 and systemd/libudev1@240-6ubuntu5.8

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* systemd/libsystemd0@240-6ubuntu5.8
  • Introduced through: buildpack-deps:19.04-scm@* systemd/libudev1@240-6ubuntu5.8

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

low severity

Improper Check for Dropped Privileges

  • Vulnerable module: bash
  • Introduced through: bash@5.0-3ubuntu1.1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* bash@5.0-3ubuntu1.1

Overview

An issue was discovered in disable_priv_mode in shell.c in GNU Bash through 5.0 patch 11. By default, if Bash is run with its effective UID not equal to its real UID, it will drop privileges by setting its effective UID to its real UID. However, it does so incorrectly. On Linux and other systems that support "saved UID" functionality, the saved UID is not dropped. An attacker with command execution in the shell can use "enable -f" for runtime loading of a new builtin, which can be a shared object that calls setuid() and therefore regains privileges. However, binaries running with an effective UID of 0 are unaffected.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-1ubuntu1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* coreutils@8.30-1ubuntu1

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

Directory Traversal

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.19.6ubuntu1.1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* dpkg@1.19.6ubuntu1.1

Overview

dpkg-source in dpkg 1.3.0 through 1.18.23 is able to use a non-GNU patch program and does not offer a protection mechanism for blank-indented diff hunks, which allows remote attackers to conduct directory traversal attacks via a crafted Debian source package, as demonstrated by use of dpkg-source on NetBSD.

References

low severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.20.1-2ubuntu1.19.04.1 and git/git-man@1:2.20.1-2ubuntu1.19.04.1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* git@1:2.20.1-2ubuntu1.19.04.1
  • Introduced through: buildpack-deps:19.04-scm@* git/git-man@1:2.20.1-2ubuntu1.19.04.1

Overview

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

References

low severity

Improper Input Validation

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.29-0ubuntu2 and glibc/libc6@2.29-0ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc-bin@2.29-0ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc6@2.29-0ubuntu2

Overview

The iconv program in the GNU C Library (aka glibc or libc6) 2.31 and earlier, when invoked with multiple suffixes in the destination encoding (TRANSLATE or IGNORE) along with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.29-0ubuntu2 and glibc/libc6@2.29-0ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc-bin@2.29-0ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc6@2.29-0ubuntu2

Overview

In the GNU C Library (aka glibc or libc6) through 2.29, the memcmp function for the x32 architecture can incorrectly return zero (indicating that the inputs are equal) because the RDX most significant bit is mishandled.

References

low severity

Out-of-bounds Read

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.29-0ubuntu2 and glibc/libc6@2.29-0ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc-bin@2.29-0ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc6@2.29-0ubuntu2

Overview

In the GNU C Library (aka glibc or libc6) through 2.29, proceed_next_node in posix/regexec.c has a heap-based buffer over-read via an attempted case-insensitive regular-expression match.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.29-0ubuntu2 and glibc/libc6@2.29-0ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc-bin@2.29-0ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc6@2.29-0ubuntu2

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.29-0ubuntu2 and glibc/libc6@2.29-0ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc-bin@2.29-0ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* glibc/libc6@2.29-0ubuntu2

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

Improper Validation of Certificate with Host Mismatch

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.12-1ubuntu3, gnupg2/gnupg@2.2.12-1ubuntu3 and others

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/dirmngr@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gnupg@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gnupg-l10n@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gnupg-utils@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg-agent@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg-wks-client@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg-wks-server@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpgconf@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpgsm@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpgv@2.2.12-1ubuntu3

Overview

Interaction between the sks-keyserver code through 1.2.0 of the SKS keyserver network, and GnuPG through 2.2.16, makes it risky to have a GnuPG keyserver configuration line referring to a host on the SKS keyserver network. Retrieving data from this network may cause a persistent denial of service, because of a Certificate Spamming Attack.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.12-1ubuntu3, gnupg2/gnupg@2.2.12-1ubuntu3 and others

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/dirmngr@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gnupg@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gnupg-l10n@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gnupg-utils@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg-agent@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg-wks-client@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpg-wks-server@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpgconf@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpgsm@2.2.12-1ubuntu3
  • Introduced through: buildpack-deps:19.04-scm@* gnupg2/gpgv@2.2.12-1ubuntu3

Overview

A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.

References

low severity

Key Management Errors

  • Vulnerable module: heimdal/libasn1-8-heimdal
  • Introduced through: heimdal/libasn1-8-heimdal@7.5.0+dfsg-2.1, heimdal/libgssapi3-heimdal@7.5.0+dfsg-2.1 and others

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libasn1-8-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libgssapi3-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libhcrypto4-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libheimbase1-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libheimntlm0-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libhx509-5-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libkrb5-26-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libroken18-heimdal@7.5.0+dfsg-2.1
  • Introduced through: buildpack-deps:19.04-scm@* heimdal/libwind0-heimdal@7.5.0+dfsg-2.1

Overview

In the client side of Heimdal before 7.6.0, failure to verify anonymous PKINIT PA-PKINIT-KX key exchange permits a man-in-the-middle attack. This issue is in krb5_init_creds_step in lib/krb5/init_creds_pw.c.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* krb5/libgssapi-krb5-2@1.17-1
  • Introduced through: buildpack-deps:19.04-scm@* krb5/libk5crypto3@1.17-1
  • Introduced through: buildpack-deps:19.04-scm@* krb5/libkrb5-3@1.17-1
  • Introduced through: buildpack-deps:19.04-scm@* krb5/libkrb5support0@1.17-1

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

Cryptographic Issues

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.4-3ubuntu1.1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* libgcrypt20@1.8.4-3ubuntu1.1

Overview

** DISPUTED ** 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.) NOTE: the vendor's position is that the issue report cannot be validated because there is no description of an attack.

References

low severity

Resource Management Errors

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.13-3

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* libtasn1-6@4.13-3

Overview

GNU Libtasn1-4.13 libtasn1-4.13 version libtasn1-4.13, libtasn1-4.12 contains a DoS, specifically CPU usage will reach 100% when running asn1Paser against the POC due to an issue in _asn1_expand_object_id(p_tree), after a long time, the program will be killed. This attack appears to be exploitable via parsing a crafted file.

References

low severity

Buffer Overflow

  • Vulnerable module: lz4/liblz4-1
  • Introduced through: lz4/liblz4-1@1.8.3-1ubuntu1

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* lz4/liblz4-1@1.8.3-1ubuntu1

Overview

LZ4 before 1.9.2 has a heap-based buffer overflow in LZ4_write32 (related to LZ4_compress_destSize), affecting applications that call LZ4_compress_fast with a large input. (This issue can also lead to data corruption.) NOTE: the vendor states "only a few specific / uncommon usages of the API are at risk."

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses6
  • Introduced through: ncurses/libncurses6@6.1+20181013-2ubuntu2, ncurses/libncursesw6@6.1+20181013-2ubuntu2 and others

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* ncurses/libncurses6@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/libncursesw6@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/libtinfo6@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/ncurses-base@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/ncurses-bin@6.1+20181013-2ubuntu2

Overview

There is a heap-based buffer over-read in the _nc_find_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

References

low severity

Out-of-bounds Read

  • Vulnerable module: ncurses/libncurses6
  • Introduced through: ncurses/libncurses6@6.1+20181013-2ubuntu2, ncurses/libncursesw6@6.1+20181013-2ubuntu2 and others

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* ncurses/libncurses6@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/libncursesw6@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/libtinfo6@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/ncurses-base@6.1+20181013-2ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* ncurses/ncurses-bin@6.1+20181013-2ubuntu2

Overview

There is a heap-based buffer over-read in the fmt_entry function in tinfo/comp_hash.c in the terminfo library in ncurses before 6.1-20191012.

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap-2.4-2
  • Introduced through: openldap/libldap-2.4-2@2.4.47+dfsg-3ubuntu2.2 and openldap/libldap-common@2.4.47+dfsg-3ubuntu2.2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openldap/libldap-2.4-2@2.4.47+dfsg-3ubuntu2.2
  • Introduced through: buildpack-deps:19.04-scm@* openldap/libldap-common@2.4.47+dfsg-3ubuntu2.2

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

Inappropriate Encoding for Output Context

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.9p1-10

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openssh/openssh-client@1:7.9p1-10

Overview

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:7.9p1-10

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openssh/openssh-client@1:7.9p1-10

Overview

Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use. NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'

References

low severity

Information Exposure

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1b-1ubuntu2.4 and openssl/libssl1.1@1.1.1b-1ubuntu2.4

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openssl@1.1.1b-1ubuntu2.4
  • Introduced through: buildpack-deps:19.04-scm@* openssl/libssl1.1@1.1.1b-1ubuntu2.4

Overview

There is an overflow bug in the x64_64 Montgomery squaring procedure used in exponentiation with 512-bit moduli. No EC algorithms are affected. Analysis suggests that attacks against 2-prime RSA1024, 3-prime RSA1536, and DSA1024 as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH512 are considered just feasible. However, for an attack the target would have to re-use the DH512 private key, which is not recommended anyway. Also applications directly using the low level API BN_mod_exp may be affected if they use BN_FLG_CONSTTIME. Fixed in OpenSSL 1.1.1e (Affected 1.1.1-1.1.1d). Fixed in OpenSSL 1.0.2u (Affected 1.0.2-1.0.2t).

References

low severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1b-1ubuntu2.4 and openssl/libssl1.1@1.1.1b-1ubuntu2.4

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openssl@1.1.1b-1ubuntu2.4
  • Introduced through: buildpack-deps:19.04-scm@* openssl/libssl1.1@1.1.1b-1ubuntu2.4

Overview

In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

References

low severity

Missing Encryption of Sensitive Data

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1b-1ubuntu2.4 and openssl/libssl1.1@1.1.1b-1ubuntu2.4

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openssl@1.1.1b-1ubuntu2.4
  • Introduced through: buildpack-deps:19.04-scm@* openssl/libssl1.1@1.1.1b-1ubuntu2.4

Overview

Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1b-1ubuntu2.4 and openssl/libssl1.1@1.1.1b-1ubuntu2.4

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* openssl@1.1.1b-1ubuntu2.4
  • Introduced through: buildpack-deps:19.04-scm@* openssl/libssl1.1@1.1.1b-1ubuntu2.4

Overview

OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* pcre3/libpcre3@2:8.39-12

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-12

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* pcre3/libpcre3@2:8.39-12

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

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* pcre3/libpcre3@2:8.39-12

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

Incorrect Permission Assignment for Critical Resource

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1.1ubuntu2 and shadow/passwd@1:4.5-1.1ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* shadow/login@1:4.5-1.1ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* shadow/passwd@1:4.5-1.1ubuntu2

Overview

An issue was discovered in shadow 4.5. newgidmap (in shadow-utils) is setuid and allows an unprivileged user to be placed in a user namespace where setgroups(2) is permitted. This allows an attacker to remove themselves from a supplementary group, which may allow access to certain filesystem paths if the administrator has used "group blacklisting" (e.g., chmod g-rwx) to restrict access to paths. This flaw effectively reverts a security feature in the kernel (in particular, the /proc/self/setgroups knob) to prevent this sort of privilege escalation.

References

low severity

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

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.5-1.1ubuntu2 and shadow/passwd@1:4.5-1.1ubuntu2

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* shadow/login@1:4.5-1.1ubuntu2
  • Introduced through: buildpack-deps:19.04-scm@* shadow/passwd@1:4.5-1.1ubuntu2

Overview

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

References

low severity

Improper Certificate Validation

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@240-6ubuntu5.8 and systemd/libudev1@240-6ubuntu5.8

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* systemd/libsystemd0@240-6ubuntu5.8
  • Introduced through: buildpack-deps:19.04-scm@* systemd/libudev1@240-6ubuntu5.8

Overview

** DISPUTED ** systemd 239 through 245 accepts any certificate signed by a trusted certificate authority for DNS Over TLS. Server Name Indication (SNI) is not sent, and there is no hostname validation with the GnuTLS backend. NOTE: This has been disputed by the developer as not a vulnerability since hostname validation does not have anything to do with this issue (i.e. there is no hostname to be sent).

References

low severity

Incorrect Privilege Assignment

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@240-6ubuntu5.8 and systemd/libudev1@240-6ubuntu5.8

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* systemd/libsystemd0@240-6ubuntu5.8
  • Introduced through: buildpack-deps:19.04-scm@* systemd/libudev1@240-6ubuntu5.8

Overview

It was discovered that a systemd service that uses DynamicUser property can create a SUID/SGID binary that would be allowed to run as the transient service UID/GID even after the service is terminated. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the UID/GID will be recycled.

References

low severity

Privilege Chaining

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@240-6ubuntu5.8 and systemd/libudev1@240-6ubuntu5.8

Detailed paths

  • Introduced through: buildpack-deps:19.04-scm@* systemd/libsystemd0@240-6ubuntu5.8
  • Introduced through: buildpack-deps:19.04-scm@* systemd/libudev1@240-6ubuntu5.8

Overview

It was discovered that a systemd service that uses DynamicUser property can get new privileges through the execution of SUID binaries, which would allow to create binaries owned by the service transient group with the setgid bit set. A local attacker may use this flaw to access resources that will be owned by a potentially different service in the future, when the GID will be recycled.

References