Image has vulnerabilities #49
Description
For DaemonSet kindnet in namespace kube-system
Description:
Image Name: docker.io/kindest/kindnetd:0.5.3
From sha256:aa67fec7d7ef71445da9a84e9bc88afca2538e9a0aebcba6ef9509b7cf313d17:
| Package | CVE | Version | Severity | Title | Description |
|---|---|---|---|---|---|
| coreutils | CVE-2016-2781 | 8.26-3 | LOW | coreutils: Non-privileged session can escape to the parent session in chroot | 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. |
| CVE-2017-18018 | LOW | coreutils: race condition vulnerability in chown and chgrp | 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. | ||
| gpgv | CVE-2018-1000858 | 2.1.18-8~deb9u4 | MEDIUM | gnupg2: Cross site request forgery in dirmngr resulting in an information disclosure or denial of service | GnuPG version 2.1.12 - 2.2.11 contains a Cross ite Request Forgery (CSRF) vulnerability in dirmngr that can result in Attacker controlled CSRF, Information Disclosure, DoS. This attack appear to be exploitable via Victim must perform a WKD request, e.g. enter an email address in the composer window of Thunderbird/Enigmail. This vulnerability appears to have been fixed in after commit 4a4bb874f63741026bd26264c43bb32b1099f060. |
| CVE-2018-9234 | MEDIUM | GnuPG: Unenforced configuration allows for apparently valid certifications actually signed by signing subkeys | 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. | ||
| CVE-2019-14855 | LOW | ||||
| libapt-pkg5.0 | CVE-2011-3374 | 1.4.9 | MEDIUM | 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. | |
| libbz2-1.0 | CVE-2019-12900 | 1.0.6-8.1 | HIGH | bzip2: out-of-bounds write in function BZ2_decompress | BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors. |
| libcomerr2 | CVE-2019-5094 | 1.43.4-2 | MEDIUM | e2fsprogs: crafted ext4 partition leads to out-of-bounds write | An exploitable code execution vulnerability exists in the quota file functionality of E2fsprogs 1.45.3. A specially crafted ext4 partition can cause an out-of-bounds write on the heap, resulting in code execution. An attacker can corrupt a partition to trigger this vulnerability. |
| CVE-2019-5188 | MEDIUM | e2fsprogs: Out-of-bounds write in e2fsck/rehash.c | 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. | ||
| libelf1 | CVE-2018-16062 | 0.168-1 | MEDIUM | elfutils: Heap-based buffer over-read in libdw/dwarf_getaranges.c:dwarf_getaranges() via crafted file | dwarf_getaranges in dwarf_getaranges.c in libdw in elfutils before 2018-08-18 allows remote attackers to cause a denial of service (heap-based buffer over-read) via a crafted file. |
| CVE-2018-16402 | HIGH | elfutils: Double-free due to double decompression of sections in crafted ELF causes crash | libelf/elf_end.c in elfutils 0.173 allows remote attackers to cause a denial of service (double free and application crash) or possibly have unspecified other impact because it tries to decompress twice. | ||
| CVE-2018-16403 | MEDIUM | elfutils: Heap-based buffer over-read in libdw/dwarf_getabbrev.c and libwd/dwarf_hasattr.c causes crash | libdw in elfutils 0.173 checks the end of the attributes list incorrectly in dwarf_getabbrev in dwarf_getabbrev.c and dwarf_hasattr in dwarf_hasattr.c, leading to a heap-based buffer over-read and an application crash. | ||
| CVE-2018-18310 | MEDIUM | elfutils: invalid memory address dereference was discovered in dwfl_segment_report_module.c in libdwfl | An invalid memory address dereference was discovered in dwfl_segment_report_module.c in libdwfl in elfutils through v0.174. The vulnerability allows attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by consider_notes. | ||
| CVE-2018-18520 | MEDIUM | elfutils: eu-size cannot handle recursive ar files | An Invalid Memory Address Dereference exists in the function elf_end in libelf in elfutils through v0.174. Although eu-size is intended to support ar files inside ar files, handle_ar in size.c closes the outer ar file before handling all inner entries. The vulnerability allows attackers to cause a denial of service (application crash) with a crafted ELF file. | ||
| CVE-2018-18521 | MEDIUM | elfutils: Divide-by-zero in arlib_add_symbols function in arlib.c | Divide-by-zero vulnerabilities in the function arlib_add_symbols() in arlib.c in elfutils 0.174 allow remote attackers to cause a denial of service (application crash) with a crafted ELF file, as demonstrated by eu-ranlib, because a zero sh_entsize is mishandled. | ||
| CVE-2019-7148 | MEDIUM | elfutils: excessive memory allocation in read_long_names in elf_begin.c in libelf | DISPUTED An attempted excessive memory allocation was discovered in the function read_long_names in elf_begin.c in libelf in elfutils 0.174. Remote attackers could leverage this vulnerability to cause a denial-of-service via crafted elf input, which leads to an out-of-memory exception. NOTE: The maintainers believe this is not a real issue, but instead a "warning caused by ASAN because the allocation is big. By setting ASAN_OPTIONS=allocator_may_return_null=1 and running the reproducer, nothing happens." | ||
| CVE-2019-7149 | MEDIUM | elfutils: heap-based buffer over-read in read_srclines in dwarf_getsrclines.c in libdw | A heap-based buffer over-read was discovered in the function read_srclines in dwarf_getsrclines.c in libdw in elfutils 0.175. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by eu-nm. | ||
| CVE-2019-7150 | MEDIUM | elfutils: segmentation fault in elf64_xlatetom in libelf/elf32_xlatetom.c | An issue was discovered in elfutils 0.175. A segmentation fault can occur in the function elf64_xlatetom in libelf/elf32_xlatetom.c, due to dwfl_segment_report_module not checking whether the dyn data read from a core file is truncated. A crafted input can cause a program crash, leading to denial-of-service, as demonstrated by eu-stack. | ||
| CVE-2019-7664 | MEDIUM | elfutils: out of bound write in elf_cvt_note in libelf/note_xlate.h | In elfutils 0.175, a negative-sized memcpy is attempted in elf_cvt_note in libelf/note_xlate.h because of an incorrect overflow check. Crafted elf input causes a segmentation fault, leading to denial of service (program crash). | ||
| CVE-2019-7665 | MEDIUM | elfutils: heap-based buffer over-read in function elf32_xlatetom in elf32_xlatetom.c | In elfutils 0.175, a heap-based buffer over-read was discovered in the function elf32_xlatetom in elf32_xlatetom.c in libelf. A crafted ELF input can cause a segmentation fault leading to denial of service (program crash) because ebl_core_note does not reject malformed core file notes. | ||
| libgcrypt20 | CVE-2018-6829 | 1.7.6-2+deb9u3 | MEDIUM | libgcrypt: ElGamal implementation doesn't have semantic security due to incorrectly encoded plaintexts possibly allowing to obtain sensitive information | 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. |
| CVE-2019-12904 | MEDIUM | Libgcrypt: physical addresses being available to other processes leads to a flush-and-reload side-channel attack | 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.) | ||
| CVE-2019-13627 | MEDIUM | libgcrypt: ECDSA timing attack in the libgcrypt20 cryptographic library | 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. | ||
| liblz4-1 | CVE-2019-17543 | 0.0~r131-2 | MEDIUM | lz4: heap-based buffer overflow in LZ4_write32 | 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." |
| libnettle6 | CVE-2018-16869 | 3.3-1 | LOW | nettle: Leaky data conversion exposing a manager oracle | A Bleichenbacher type side-channel based padding oracle attack was found in the way nettle handles endian conversion of RSA decrypted PKCS#1 v1.5 data. An attacker who is able to run a process on the same physical core as the victim process, could use this flaw extract plaintext or in some cases downgrade any TLS connections to a vulnerable server. |
| libpcre3 | CVE-2017-11164 | 2:8.39-3 | HIGH | pcre: OP_KETRMAX feature in the match function in pcre_exec.c | 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. |
| CVE-2017-16231 | LOW | pcre: self-recursive call in match() in pcre_exec.c leads to denial of service | ** 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. | ||
| CVE-2017-7245 | MEDIUM | pcre: stack-based buffer overflow write in pcre32_copy_substring | 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. | ||
| CVE-2017-7246 | MEDIUM | pcre: stack-based buffer overflow write in pcre32_copy_substring | 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. | ||
| libstdc++6 | CVE-2018-12886 | 6.3.0-18+deb9u1 | MEDIUM | gcc: spilling of stack protection address in cfgexpand.c and function.c leads to stack-overflow protection bypass | 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. |
| libtinfo5 | CVE-2018-19211 | 6.0+20161126-1+deb9u2 | MEDIUM | ncurses: Null pointer dereference at function _nc_parse_entry in parse_entry.c | 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. |
| CVE-2019-17594 | MEDIUM | ncurses: heap-based buffer overflow in the _nc_find_entry function in tinfo/comp_hash.c | 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. | ||
| CVE-2019-17595 | MEDIUM | ncurses: heap-based buffer overflow in the fmt_entry function in tinfo/comp_hash.c | 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. | ||
| libuuid1 | CVE-2016-2779 | 2.29.2-1+deb9u1 | HIGH | util-linux: runuser tty hijack via TIOCSTI ioctl | runuser in util-linux allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. |
| libxtables12 | CVE-2012-2663 | 1.6.0+snapshot20161117-6 | HIGH | iptables: --syn flag bypass | 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. |
| CVE-2019-11360 | MEDIUM | 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. | |||
| multiarch-support | CVE-2009-5155 | 2.24-11+deb9u4 | MEDIUM | glibc: parse_reg_exp in posix/regcomp.c misparses alternatives leading to denial of service or trigger incorrect result | In the GNU C Library (aka glibc or libc6) before 2.28, parse_reg_exp in posix/regcomp.c misparses alternatives, which allows attackers to cause a denial of service (assertion failure and application exit) or trigger an incorrect result by attempting a regular-expression match. |
| CVE-2010-4051 | MEDIUM | CVE-2010-4052 glibc: De-recursivise regular expression engine | 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." | ||
| CVE-2010-4052 | MEDIUM | CVE-2010-4051 CVE-2010-4052 glibc: De-recursivise regular expression engine | 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. | ||
| CVE-2010-4756 | MEDIUM | glibc: glob implementation can cause excessive CPU and memory consumption due to crafted glob expressions | 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. | ||
| CVE-2015-8985 | MEDIUM | glibc: potential denial of service in pop_fail_stack() | 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. | ||
| CVE-2016-10228 | MEDIUM | glibc: iconv program can hang when invoked with the -c option | The iconv program in the GNU C Library (aka glibc or libc6) 2.25 and earlier, when invoked with the -c option, enters an infinite loop when processing invalid multi-byte input sequences, leading to a denial of service. | ||
| CVE-2016-10739 | MEDIUM | glibc: getaddrinfo should reject IP addresses with trailing characters | In the GNU C Library (aka glibc or libc6) through 2.28, the getaddrinfo function would successfully parse a string that contained an IPv4 address followed by whitespace and arbitrary characters, which could lead applications to incorrectly assume that it had parsed a valid string, without the possibility of embedded HTTP headers or other potentially dangerous substrings. | ||
| CVE-2017-12132 | MEDIUM | glibc: Fragmentation attacks possible when EDNS0 is enabled | The DNS stub resolver in the GNU C Library (aka glibc or libc6) before version 2.26, when EDNS support is enabled, will solicit large UDP responses from name servers, potentially simplifying off-path DNS spoofing attacks due to IP fragmentation. | ||
| CVE-2018-1000001 | HIGH | glibc: realpath() buffer underflow when getcwd() returns relative path allows privilege escalation | In glibc 2.26 and earlier there is confusion in the usage of getcwd() by realpath() which can be used to write before the destination buffer leading to a buffer underflow and potential code execution. | ||
| CVE-2018-20796 | MEDIUM | glibc: uncontrolled recursion in function check_dst_limits_calc_pos_1 in posix/regexec.c | 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 | ||
| CVE-2018-6485 | HIGH | glibc: Integer overflow in posix_memalign in memalign functions | An integer overflow in the implementation of the posix_memalign in memalign functions in the GNU C Library (aka glibc or libc6) 2.26 and earlier could cause these functions to return a pointer to a heap area that is too small, potentially leading to heap corruption. | ||
| CVE-2018-6551 | HIGH | glibc: integer overflow in malloc functions | The malloc implementation in the GNU C Library (aka glibc or libc6), from version 2.24 to 2.26 on powerpc, and only in version 2.26 on i386, did not properly handle malloc calls with arguments close to SIZE_MAX and could return a pointer to a heap region that is smaller than requested, eventually leading to heap corruption. | ||
| CVE-2019-1010022 | HIGH | glibc: stack guard protection bypass | 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. | ||
| CVE-2019-1010023 | MEDIUM | glibc: running ldd on malicious ELF leads to code execution because of wrong size computation | GNU Libc current is affected by: Re-mapping current loaded libray 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. | ||
| CVE-2019-1010024 | MEDIUM | glibc: ASLR bypass using cache of thread stack and heap | 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. | ||
| CVE-2019-1010025 | MEDIUM | glibc: information disclosure of heap addresses of pthread_created thread | ** 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." | ||
| CVE-2019-19126 | LOW | glibc: LD_PREFER_MAP_32BIT_EXEC not ignored in setuid binaries | 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. | ||
| CVE-2019-6488 | MEDIUM | glibc: Incorrect attempt to use a 64-bit register for size_t in assembly codes results in segmentation fault | 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. | ||
| CVE-2019-7309 | LOW | glibc: memcmp function incorrectly returns zero | 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. | ||
| CVE-2019-9169 | HIGH | glibc: regular-expression match via proceed_next_node in posix/regexec.c leads to heap-based buffer over-read | 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. | ||
| CVE-2019-9192 | MEDIUM | glibc: uncontrolled recursion in function check_dst_limits_calc_pos_1 in posix/regexec.c | ** 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 '( | ||
| passwd | CVE-2007-5686 | 1:4.4-4.1 | MEDIUM | 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. | |
| CVE-2013-4235 | LOW | shadow-utils: TOCTOU race conditions by copying and removing directory trees | shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees | ||
| CVE-2017-12424 | HIGH | shadow-utils: Buffer overflow via newusers tool | In shadow before 4.5, the newusers tool could be made to manipulate internal data structures in ways unintended by the authors. Malformed input may lead to crashes (with a buffer overflow or other memory corruption) or other unspecified behaviors. This crosses a privilege boundary in, for example, certain web-hosting environments in which a Control Panel allows an unprivileged user account to create subaccounts. | ||
| CVE-2018-7169 | MEDIUM | shadow-utils: newgidmap allows unprivileged user to drop supplementary groups potentially allowing privilege escalation | 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. | ||
| CVE-2019-19882 | MEDIUM | shadow-utils: local users can obtain root access because setuid programs are misconfigured | 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). | ||
| TEMP-0628843-DBAD28 | LOW | ||||
| perl-base | CVE-2011-4116 | 5.24.1-3+deb9u5 | MEDIUM | perl: File::Temp insecure temporary file handling | _is_safe in the File::Temp module for Perl does not properly handle symlinks. |
| tar | CVE-2005-2541 | 1.29b-1.1 | CRITICAL | 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. | |
| CVE-2018-20482 | LOW | tar: Infinite read loop in sparse_dump_region function in sparse.c | GNU Tar through 1.30, when --sparse is used, mishandles file shrinkage during read access, which allows local users to cause a denial of service (infinite read loop in sparse_dump_region in sparse.c) by modifying a file that is supposed to be archived by a different user's process (e.g., a system backup running as root). | ||
| CVE-2019-9923 | MEDIUM | tar: null-pointer dereference in pax_decode_header in sparse.c | 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. | ||
| TEMP-0290435-0B57B5 | LOW |
Remediation:
If this image is from a third-party application or Helm chart, try updating
to the latest version. If this doesn't solve the issue, let the maintainers
know that the image they're using may contain vulnerabilities, e.g. by
filing an issue on GitHub.
If this image is from an application you own, try updating the base image (currently debian 9.8),
as well as any libraries you're installing on top of it. If this doesn't solve
the issue, let the maintainer of the base image or offending libraries
know, e.g. by filing an issue on GitHub.