Docker debian:stretch-20190610-slim

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

• Debian Bug Report
• Debian Security Tracker
• MISC
• MISC
• RedHat CVE Database

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

• CONFIRM
• Debian Security Tracker
• GitHub Commit
• MISC
• MISC
• Ubuntu CVE Tracker

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

• Debian Security Tracker
• OSS security Advisory
• OSS security Advisory
• Ubuntu CVE Tracker

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

• CVE Details
• Debian Security Tracker
• http://lists.gnu.org/archive/html/coreutils/2017-12/msg00045.html

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

• CONFIRM
• Debian Security Tracker
• MISC
• Security Focus
• UBUNTU

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

• BUGTRAQ
• Cert Vulnerability Note
• Dead Link
• Debian Security Tracker
• Exploit DB
• MISC
• RedHat Bugzilla Bug
• SECTRACK
• SREASON
• SREASONRES
• Seclists Full Disclosure
• Secunia Advisory
• Security Focus

Overview

Affected versions of this package are vulnerable to CVE-2020-27618.

Remediation

There is no fixed version for glibc.

References

• ADVISORY

Overview

The pop_fail_stack function in the GNU C Library (aka glibc or libc6) allows context-dependent attackers to cause a denial of service (assertion failure and application crash) via vectors related to extended regular expression processing.

References

• Debian Bug Report
• Debian Security Tracker
• Gentoo Security Advisory
• OSS security Advisory
• Security Focus
• Ubuntu CVE Tracker

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

• CONFIRM
• CONFIRM
• Debian Security Tracker
• OSS security Advisory
• Security Focus
• Ubuntu CVE Tracker
• https://sourceware.org/bugzilla/show_bug.cgi?id=19519

Overview

The string component in the GNU C Library (aka glibc or libc6) through 2.28, when running on the x32 architecture, incorrectly attempts to use a 64-bit register for size_t in assembly codes, which can lead to a segmentation fault or possibly unspecified other impact, as demonstrated by a crash in __memmove_avx_unaligned_erms in sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S during a memcpy.

References

• Debian Security Tracker
• GENTOO
• MISC
• Security Focus

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

• CONFIRM
• CONFIRM
• Debian Security Tracker
• MISC
• Security Focus
• UBUNTU

Overview

On the x86-64 architecture, the GNU C Library (aka glibc) before 2.31 fails to ignore the LD_PREFER_MAP_32BIT_EXEC environment variable during program execution after a security transition, allowing local attackers to restrict the possible mapping addresses for loaded libraries and thus bypass ASLR for a setuid program.

References

• Debian Security Tracker
• FEDORA
• Fedora Security Update
• MISC
• UBUNTU
• Ubuntu CVE Tracker

Overview

An exploitable signed comparison vulnerability exists in the ARMv7 memcpy() implementation of GNU glibc 2.30.9000. Calling memcpy() (on ARMv7 targets that utilize the GNU glibc implementation) with a negative value for the 'num' parameter results in a signed comparison vulnerability. If an attacker underflows the 'num' parameter to memcpy(), this vulnerability could lead to undefined behavior such as writing to out-of-bounds memory and potentially remote code execution. Furthermore, this memcpy() implementation allows for program execution to continue in scenarios where a segmentation fault or crash should have occurred. The dangers occur in that subsequent execution and iterations of this code will be executed with this corrupted data.

References

• Debian Security Tracker
• FEDORA
• FEDORA
• MISC
• MISC

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

• Debian Security Tracker
• GENTOO
• MISC
• MISC
• Security Focus
• Ubuntu CVE Tracker

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

• Debian Security Tracker
• MISC
• UBUNTU

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

• BUGTRAQ
• Cert Vulnerability Note
• Dead Link
• Debian Security Tracker
• Exploit DB
• MISC
• RedHat Bugzilla Bug
• SECTRACK
• SREASON
• SREASONRES
• Seclists Full Disclosure
• Secunia Advisory
• Security Focus

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

• Debian Security Tracker
• http://cxib.net/stuff/glob-0day.c
• http://securityreason.com/achievement_securityalert/89
• http://securityreason.com/exploitalert/9223

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

• CONFIRM
• Debian Security Tracker
• MISC
• Ubuntu CVE Tracker

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

• CONFIRM
• Debian Security Tracker
• MISC
• MISC
• Netapp Security Advisory
• Security Focus
• Ubuntu CVE Tracker

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

• CONFIRM
• CONFIRM
• Debian Security Tracker
• MISC
• UBUNTU

Overview

GnuPG 2.2.4 and 2.2.5 does not enforce a configuration in which key certification requires an offline master Certify key, which results in apparently valid certifications that occurred only with access to a signing subkey.

References

• Debian Security Tracker
• MISC
• Ubuntu CVE Tracker
• Ubuntu Security Advisory

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

• ADVISORY
• Debian Security Tracker
• MISC
• MISC
• MISC
• RedHat Bugzilla Bug
• UBUNTU
• Ubuntu CVE Tracker

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

• Debian Security Tracker
• MISC
• MISC
• MISC
• MISC

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

• ADVISORY
• Apache Security Advisory
• Apache Security Advisory
• Apache Security Advisory
• Apache Security Advisory
• Apache Security Advisory
• Debian Security Tracker
• GitHub Diff
• GitHub Issue
• GitHub PR
• GitHub PR
• MISC
• MISC
• MISC
• MLIST
• MLIST
• MLIST
• OpenSuse Security Announcement
• OpenSuse Security Announcement
• Ubuntu CVE Tracker

Overview

In ncurses 6.1, there is a NULL pointer dereference at function _nc_parse_entry in parse_entry.c that will lead to a denial of service attack. The product proceeds to the dereference code path even after a "dubious character `*' in name or alias field" detection.

References

• Debian Security Tracker
• RedHat Bugzilla Bug

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

• Debian Security Tracker
• MISC
• MISC
• OpenSuse Security Announcement
• OpenSuse Security Announcement
• Ubuntu CVE Tracker

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

• Debian Security Tracker
• MISC
• MISC
• OpenSuse Security Announcement
• OpenSuse Security Announcement
• Ubuntu CVE Tracker

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

• CVE Details
• Debian Security Tracker
• Gentoo Security Advisory
• MISC
• RHSA Security Advisory
• Security Focus
• Ubuntu CVE Tracker

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

• CVE Details
• Debian Security Tracker
• Gentoo Security Advisory
• MISC
• RHSA Security Advisory
• Security Focus
• Ubuntu CVE Tracker

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

• CONFIRM
• CVE Details
• Debian Security Tracker
• MISC
• OSS security Advisory
• OSS security Advisory
• OSS security Advisory
• OSS security Advisory
• Seclists Full Disclosure
• Security Focus

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

• ADVISORY
• ADVISORY
• CONFIRM
• FULLDISC
• MISC
• MISC

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

• CVE Details
• Debian Security Tracker
• OSS security Advisory
• Security Focus
• Ubuntu CVE Tracker

Overview

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

References

• Debian Security Tracker
• GitHub Issue
• MISC
• OSS security Advisory
• OSS security Advisory
• Oss-Sec Mailing List

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

• BUGTRAQ
• BUGTRAQ
• CONFIRM
• Dead Link
• Dead Link
• Debian Security Tracker
• Secunia Advisory
• Security Focus
• VUPEN

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

• Debian Security Tracker
• Gentoo Security Advisory
• MISC
• Ubuntu CVE Tracker

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

• Debian Security Tracker
• GENTOO
• GitHub Commit
• GitHub PR
• GitHub PR
• MISC
• MISC

Overview

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

References

• Debian Security Tracker
• RedHat Bugzilla Bug
• RedHat CVE Database
• Ubuntu CVE Tracker

Overview

systemd-tmpfiles in systemd through 237 mishandles symlinks present in non-terminal path components, which allows local users to obtain ownership of arbitrary files via vectors involving creation of a directory and a file under that directory, and later replacing that directory with a symlink. This occurs even if the fs.protected_symlinks sysctl is turned on.

References

• Debian Security Tracker
• GitHub Issue
• OpenSuse Security Announcement
• Ubuntu CVE Tracker
• Ubuntu Security Advisory
• Ubuntu Security Advisory

Overview

CVE-2019-9619

References

• Debian Security Tracker

Overview

It was discovered systemd does not correctly check the content of PIDFile files before using it to kill processes. When a service is run from an unprivileged user (e.g. User field set in the service file), a local attacker who is able to write to the PIDFile of the mentioned service may use this flaw to trick systemd into killing other services and/or privileged processes. Versions before v237 are vulnerable.

References

• Apache Security Advisory
• Debian Security Tracker
• Netapp Security Advisory
• RHSA Security Advisory
• RedHat Bugzilla Bug
• UBUNTU
• Ubuntu CVE Tracker

Overview

systemd v233 and earlier fails to safely parse usernames starting with a numeric digit (e.g. "0day"), running the service in question with root privileges rather than the user intended.

References

• Debian Security Tracker
• GitHub Issue
• OSS security Advisory
• Security Focus
• Security Tracker

Overview

Affected versions of this package are vulnerable to Improper Input Validation systemd through v245 mishandles numerical usernames such as ones composed of decimal digits or 0x followed by hex digits, as demonstrated by use of root privileges when privileges of the 0x0 user account were intended. NOTE: this issue exists because of an incomplete fix for CVE-2017-1000082.

Remediation

There is no fixed version for systemd.

References

• ADVISORY
• CONFIRM
• Debian Security Tracker
• FEDORA
• GitHub Issue

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

• Debian Bug Report
• Debian Security Tracker
• OSS security Advisory
• RedHat Bugzilla Bug

Overview

systemd-tmpfiles in systemd before 237 attempts to support ownership/permission changes on hardlinked files even if the fs.protected_hardlinks sysctl is turned off, which allows local users to bypass intended access restrictions via vectors involving a hard link to a file for which the user lacks write access, as demonstrated by changing the ownership of the /etc/passwd file.

References

• Debian Security Announcement
• Debian Security Tracker
• Exploit DB
• GitHub Issue
• MISC
• OSS security Advisory
• OSS security Advisory
• OpenSuse Security Update

Overview

An issue was discovered in button_open in login/logind-button.c in systemd before 243. When executing the udevadm trigger command, a memory leak may occur.

References

• Debian Security Tracker
• FEDORA
• GitHub Commit
• Netapp Security Advisory
• OpenSuse Security Announcement
• Ubuntu CVE Tracker
• Ubuntu Security Advisory

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

• Debian Security Tracker
• HP Security Bulletin

Overview

Affected versions of this package are vulnerable to CVE-2021-20193.

Remediation

There is no fixed version for tar.

References

• ADVISORY

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

• Debian Security Tracker
• MISC
• MISC
• MISC
• OpenSuse Security Announcement
• Ubuntu CVE Tracker