Docker debian:10.4
Vulnerabilities |
63 via 97 paths |
---|---|
Dependencies |
91 |
Source |
Docker |
Target OS |
debian:10 |
high severity
- Vulnerable module: gcc-8/gcc-8-base
- Introduced through: gcc-8/gcc-8-base@8.3.0-6, gcc-8/libgcc1@1:8.3.0-6 and others
Detailed paths
-
Introduced through: debian:10.4@* › gcc-8/gcc-8-base@8.3.0-6
-
Introduced through: debian:10.4@* › gcc-8/libgcc1@1:8.3.0-6
-
Introduced through: debian:10.4@* › gcc-8/libstdc++6@8.3.0-6
Overview
stack_protect_prologue in cfgexpand.c and stack_protect_epilogue in function.c in GNU Compiler Collection (GCC) 4.1 through 8 (under certain circumstances) generate instruction sequences when targeting ARM targets that spill the address of the stack protector guard, which allows an attacker to bypass the protection of -fstack-protector, -fstack-protector-all, -fstack-protector-strong, and -fstack-protector-explicit against stack overflow by controlling what the stack canary is compared against.
References
high severity
- Vulnerable module: gcc-8/gcc-8-base
- Introduced through: gcc-8/gcc-8-base@8.3.0-6, gcc-8/libgcc1@1:8.3.0-6 and others
Detailed paths
-
Introduced through: debian:10.4@* › gcc-8/gcc-8-base@8.3.0-6
-
Introduced through: debian:10.4@* › gcc-8/libgcc1@1:8.3.0-6
-
Introduced through: debian:10.4@* › gcc-8/libstdc++6@8.3.0-6
Overview
The POWER9 backend in GNU Compiler Collection (GCC) before version 10 could optimize multiple calls of the __builtin_darn intrinsic into a single call, thus reducing the entropy of the random number generator. This occurred because a volatile operation was not specified. For example, within a single execution of a program, the output of every __builtin_darn() call may be the same.
References
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
Overview
An out-of-bounds write vulnerability was found in glibc before 2.31 when handling signal trampolines on PowerPC. Specifically, the backtrace function did not properly check the array bounds when storing the frame address, resulting in a denial of service or potential code execution. The highest threat from this vulnerability is to system availability.
References
high severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
Overview
A use-after-free vulnerability introduced in glibc upstream version 2.14 was found in the way the tilde expansion was carried out. Directory paths containing an initial tilde followed by a valid username were affected by this issue. A local attacker could exploit this flaw by creating a specially crafted path that, when processed by the glob function, would potentially lead to arbitrary code execution. This was fixed in version 2.32.
References
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › gnutls28/libgnutls30@3.6.7-4+deb10u4
Overview
Affected versions of this package are vulnerable to Out-of-bounds Write. An issue was discovered in GnuTLS before 3.6.15. A server can trigger a NULL pointer dereference in a TLS 1.3 client if a no_renegotiation alert is sent with unexpected timing, and then an invalid second handshake occurs. The crash happens in the application's error handling path, where the gnutls_deinit function is called after detecting a handshake failure.
Remediation
There is no fixed version for gnutls28
.
References
high severity
- Vulnerable module: libidn2/libidn2-0
- Introduced through: libidn2/libidn2-0@2.0.5-1+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › libidn2/libidn2-0@2.0.5-1+deb10u1
Overview
GNU libidn2 before 2.2.0 fails to perform the roundtrip checks specified in RFC3490 Section 4.2 when converting A-labels to U-labels. This makes it possible in some circumstances for one domain to impersonate another. By creating a malicious domain that matches a target domain except for the inclusion of certain punycoded Unicode characters (that would be discarded when converted first to a Unicode label and then back to an ASCII label), arbitrary domains can be impersonated.
References
high severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.23.15-2
- Fixed in: 0.23.15-2+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › p11-kit/libp11-kit0@0.23.15-2
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound. An issue was discovered in p11-kit 0.21.1 through 0.23.21. Multiple integer overflows have been discovered in the array allocations in the p11-kit library and the p11-kit list command, where overflow checks are missing before calling realloc or calloc.
Remediation
Upgrade p11-kit
to version or higher.
References
high severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.23.15-2
- Fixed in: 0.23.15-2+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › p11-kit/libp11-kit0@0.23.15-2
Overview
Affected versions of this package are vulnerable to Out-of-bounds Write. An issue was discovered in p11-kit 0.23.6 through 0.23.21. A heap-based buffer overflow has been discovered in the RPC protocol used by p11-kit server/remote commands and the client library. When the remote entity supplies a serialized byte array in a CK_ATTRIBUTE, the receiving entity may not allocate sufficient length for the buffer to store the deserialized value.
Remediation
Upgrade p11-kit
to version or higher.
References
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.28.1-6
- Fixed in: 5.28.1-6+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › perl/perl-base@5.28.1-6
Overview
Affected versions of this package are vulnerable to Buffer Overflow regcomp.c in Perl before 5.30.3 allows a buffer overflow via a crafted regular expression because of recursive S_study_chunk calls.
Remediation
Upgrade perl
to version or higher.
References
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.28.1-6
- Fixed in: 5.28.1-6+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › perl/perl-base@5.28.1-6
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound. Perl before 5.30.3 has an integer overflow related to mishandling of a "PL_regkind[OP(n)] == NOTHING" situation. A crafted regular expression could lead to malformed bytecode with a possibility of instruction injection.
Remediation
Upgrade perl
to version or higher.
References
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.28.1-6
- Fixed in: 5.28.1-6+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › perl/perl-base@5.28.1-6
Overview
Affected versions of this package are vulnerable to Out-of-bounds Write. Perl before 5.30.3 on 32-bit platforms allows a heap-based buffer overflow because nested regular expression quantifiers have an integer overflow.
Remediation
Upgrade perl
to version or higher.
References
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
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
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
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
high severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
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
medium severity
- Vulnerable module: apt
- Introduced through: apt@1.8.2.1 and apt/libapt-pkg5.0@1.8.2.1
- Fixed in: 1.8.2.2
Detailed paths
-
Introduced through: debian:10.4@* › apt@1.8.2.1
-
Introduced through: debian:10.4@* › apt/libapt-pkg5.0@1.8.2.1
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound. APT had several integer overflows and underflows while parsing .deb packages, aka GHSL-2020-168 GHSL-2020-169, in files apt-pkg/contrib/extracttar.cc, apt-pkg/deb/debfile.cc, and apt-pkg/contrib/arfile.cc. This issue affects: apt 1.2.32ubuntu0 versions prior to 1.2.32ubuntu0.2; 1.6.12ubuntu0 versions prior to 1.6.12ubuntu0.2; 2.0.2ubuntu0 versions prior to 2.0.2ubuntu0.2; 2.1.10ubuntu0 versions prior to 2.1.10ubuntu0.1;
Remediation
Upgrade apt
to version or higher.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
Overview
The GNU C Library (aka glibc or libc6) before 2.32 could overflow an on-stack buffer during range reduction if an input to an 80-bit long double function contains a non-canonical bit pattern, a seen when passing a 0x5d414141414141410000 value to sinl on x86 targets. This is related to sysdeps/ieee754/ldbl-96/e_rem_pio2l.c.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
Overview
Affected versions of this package are vulnerable to Out-of-bounds Read. The iconv feature in the GNU C Library (aka glibc or libc6) through 2.32, when processing invalid multi-byte input sequences in the EUC-KR encoding, may have a buffer over-read.
Remediation
There is no fixed version for glibc
.
References
medium severity
- Vulnerable module: iproute2
- Introduced through: iproute2@4.20.0-2
Detailed paths
-
Introduced through: debian:10.4@* › iproute2@4.20.0-2
Overview
iproute2 before 5.1.0 has a use-after-free in get_netnsid_from_name in ip/ipnetns.c. NOTE: security relevance may be limited to certain uses of setuid that, although not a default, are sometimes a configuration option offered to end users. Even when setuid is used, other factors (such as C library configuration) may block exploitability.
References
medium severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.8.4-5
Detailed paths
-
Introduced through: debian:10.4@* › libgcrypt20@1.8.4-5
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
medium severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.8.4-5
Detailed paths
-
Introduced through: debian:10.4@* › libgcrypt20@1.8.4-5
Overview
It was discovered that there was a ECDSA timing attack in the libgcrypt20 cryptographic library. Version affected: 1.8.4-5, 1.7.6-2+deb9u3, and 1.6.3-2+deb8u4. Versions fixed: 1.8.5-2 and 1.6.3-2+deb8u7.
References
- ADVISORY
- Debian Security Announcement
- Debian Security Announcement
- Debian Security Tracker
- Gentoo Security Advisory
- GitHub Release
- MISC
- OSS security Advisory
- OpenSuse Security Announcement
- OpenSuse Security Announcement
- Ubuntu CVE Tracker
- Ubuntu Security Advisory
- Ubuntu Security Advisory
- Ubuntu Security Advisory
medium severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.23.15-2
- Fixed in: 0.23.15-2+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › p11-kit/libp11-kit0@0.23.15-2
Overview
Affected versions of this package are vulnerable to Out-of-bounds Read. An issue was discovered in p11-kit 0.21.1 through 0.23.21. A heap-based buffer over-read has been discovered in the RPC protocol used by thep11-kit server/remote commands and the client library. When the remote entity supplies a byte array through a serialized PKCS#11 function call, the receiving entity may allow the reading of up to 4 bytes of memory past the heap allocation.
Remediation
Upgrade p11-kit
to version or higher.
References
medium severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12
Detailed paths
-
Introduced through: debian:10.4@* › pcre3/libpcre3@2:8.39-12
Overview
Affected versions of this package are vulnerable to Integer Overflow or Wraparound libpcre in PCRE before 8.44 allows an integer overflow via a large number after a (?C substring.
Remediation
There is no fixed version for pcre3
.
References
low severity
- Vulnerable module: apt
- Introduced through: apt@1.8.2.1 and apt/libapt-pkg5.0@1.8.2.1
Detailed paths
-
Introduced through: debian:10.4@* › apt@1.8.2.1
-
Introduced through: debian:10.4@* › apt/libapt-pkg5.0@1.8.2.1
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
- Vulnerable module: bash
- Introduced through: bash@5.0-4
Detailed paths
-
Introduced through: debian:10.4@* › bash@5.0-4
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
- Vulnerable module: coreutils
- Introduced through: coreutils@8.30-3
Detailed paths
-
Introduced through: debian:10.4@* › coreutils@8.30-3
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
- Vulnerable module: coreutils
- Introduced through: coreutils@8.30-3
Detailed paths
-
Introduced through: debian:10.4@* › coreutils@8.30-3
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
Overview
Affected versions of this package are vulnerable to CVE-2020-27618.
Remediation
There is no fixed version for glibc
.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.28-10 and glibc/libc6@2.28-10
Detailed paths
-
Introduced through: debian:10.4@* › glibc/libc-bin@2.28-10
-
Introduced through: debian:10.4@* › glibc/libc6@2.28-10
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
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.12-1+deb10u1
Detailed paths
-
Introduced through: debian:10.4@* › gnupg2/gpgv@2.2.12-1+deb10u1
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
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.7-4+deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › gnutls28/libgnutls30@3.6.7-4+deb10u4
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
- APPLE
- APPLE
- Apple Security Advisory
- Apple Security Advisory
- Apple Security Advisory
- Apple Security Advisory
- Apple Security Advisory
- Apple Security Advisory
- Apple Security Announcement
- Apple Security Announcement
- Apple Security Announcement
- Apple Security Announcement
- Apple Security Announcement
- CERT
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- CONFIRM
- Cert Vulnerability Note
- Chrome Release
- Debian Security Advisory
- Debian Security Tracker
- Gentoo Security Advisory
- Gentoo Security Advisory
- HP
- HP Security Bulletin
- HP Security Bulletin
- HP Security Bulletin
- HP Security Bulletin
- HP Security Bulletin
- HP Security Bulletin
- MANDRIVA
- MISC
- MISC
- MISC
- MISC
- MISC
- MISC
- MISC
- MISC
- MS
- MS
- OSVDB
- OpenSuse Security Announcement
- OpenSuse Security Announcement
- OpenSuse Security Announcement
- Oracle Security Bulletin
- Oracle Security Bulletin
- Oracle Security Bulletin
- Oval Security
- REDHAT
- REDHAT
- RedHat Bugzilla Bug
- RedHat Security Advisory
- RedHat Security Advisory
- SUSE
- SUSE
- SUSE
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Secunia Advisory
- Security Focus
- Security Focus
- Security Tracker
- Security Tracker
- Security Tracker
- Security Tracker
- Ubuntu CVE Tracker
- Ubuntu Security Advisory
low severity
- Vulnerable module: iptables/libxtables12
- Introduced through: iptables/libxtables12@1.8.2-4
Detailed paths
-
Introduced through: debian:10.4@* › iptables/libxtables12@1.8.2-4
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
- Vulnerable module: iptables/libxtables12
- Introduced through: iptables/libxtables12@1.8.2-4
Detailed paths
-
Introduced through: debian:10.4@* › iptables/libxtables12@1.8.2-4
Overview
A buffer overflow in iptables-restore in netfilter iptables 1.8.2 allows an attacker to (at least) crash the program or potentially gain code execution via a specially crafted iptables-save file. This is related to add_param_to_argv in xshared.c.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.8.4-5
Detailed paths
-
Introduced through: debian:10.4@* › libgcrypt20@1.8.4-5
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
- Vulnerable module: libseccomp/libseccomp2
- Introduced through: libseccomp/libseccomp2@2.3.3-4
Detailed paths
-
Introduced through: debian:10.4@* › libseccomp/libseccomp2@2.3.3-4
Overview
libseccomp before 2.4.0 did not correctly generate 64-bit syscall argument comparisons using the arithmetic operators (LT, GT, LE, GE), which might able to lead to bypassing seccomp filters and potential privilege escalations.
References
low severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.13-3
Detailed paths
-
Introduced through: debian:10.4@* › 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
- Vulnerable module: lz4/liblz4-1
- Introduced through: lz4/liblz4-1@1.8.3-1
Detailed paths
-
Introduced through: debian:10.4@* › lz4/liblz4-1@1.8.3-1
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
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12
Detailed paths
-
Introduced through: debian:10.4@* › 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
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12
Detailed paths
-
Introduced through: debian:10.4@* › 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
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12
Detailed paths
-
Introduced through: debian:10.4@* › pcre3/libpcre3@2:8.39-12
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
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12
Detailed paths
-
Introduced through: debian:10.4@* › pcre3/libpcre3@2:8.39-12
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
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12
Detailed paths
-
Introduced through: debian:10.4@* › 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
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.28.1-6
Detailed paths
-
Introduced through: debian:10.4@* › perl/perl-base@5.28.1-6
Overview
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
Detailed paths
-
Introduced through: debian:10.4@* › shadow/login@1:4.5-1.1
-
Introduced through: debian:10.4@* › shadow/passwd@1:4.5-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
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
Detailed paths
-
Introduced through: debian:10.4@* › shadow/login@1:4.5-1.1
-
Introduced through: debian:10.4@* › shadow/passwd@1:4.5-1.1
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
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
Detailed paths
-
Introduced through: debian:10.4@* › shadow/login@1:4.5-1.1
-
Introduced through: debian:10.4@* › shadow/passwd@1:4.5-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
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.5-1.1 and shadow/passwd@1:4.5-1.1
Detailed paths
-
Introduced through: debian:10.4@* › shadow/login@1:4.5-1.1
-
Introduced through: debian:10.4@* › shadow/passwd@1:4.5-1.1
Overview
shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
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
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
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
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@241-7~deb10u4 and systemd/libudev1@241-7~deb10u4
Detailed paths
-
Introduced through: debian:10.4@* › systemd/libsystemd0@241-7~deb10u4
-
Introduced through: debian:10.4@* › systemd/libudev1@241-7~deb10u4
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
low severity
- Vulnerable module: tar
- Introduced through: tar@1.30+dfsg-6
Detailed paths
-
Introduced through: debian:10.4@* › tar@1.30+dfsg-6
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
- Vulnerable module: tar
- Introduced through: tar@1.30+dfsg-6
Detailed paths
-
Introduced through: debian:10.4@* › tar@1.30+dfsg-6
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.