Docker Image
Status as of
The following known vulnerabilities were found:
| CVE ID | Severity | Package | Details | Summary | Mitigation |
|---|---|---|---|---|---|
| CVE-2011-3389 | Low | gnutls28 | https://scout.docker.com/v/CVE-2011-3389 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2023-31439 | Low | systemd | https://scout.docker.com/v/CVE-2023-31439 | An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability." | We are currently waiting for a fix from the vendor. |
| CVE-2023-31438 | Low | systemd | https://scout.docker.com/v/CVE-2023-31438 | An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability." | We are currently waiting for a fix from the vendor. |
| CVE-2023-31437 | Low | systemd | https://scout.docker.com/v/CVE-2023-31437 | An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability." | We are currently waiting for a fix from the vendor. |
| CVE-2013-4392 | Low | systemd | https://scout.docker.com/v/CVE-2013-4392 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2020-15719 | Low | openldap | https://scout.docker.com/v/CVE-2020-15719 | libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux. | We are currently waiting for a fix from the vendor. |
| CVE-2017-17740 | Low | openldap | https://scout.docker.com/v/CVE-2017-17740 | contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation. | We are currently waiting for a fix from the vendor. |
| CVE-2017-14159 | Low | openldap | https://scout.docker.com/v/CVE-2017-14159 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2015-3276 | Low | openldap | https://scout.docker.com/v/CVE-2015-3276 | The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors. | We are currently waiting for a fix from the vendor. |
| CVE-2007-5686 | Low | shadow | https://scout.docker.com/v/CVE-2007-5686 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2025-27587 | Low | openssl | https://scout.docker.com/v/CVE-2025-27587 | OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system. | We are currently waiting for a fix from the vendor. |
| CVE-2010-0928 | Low | openssl | https://scout.docker.com/v/CVE-2010-0928 | OpenSSL 0.9.8i on the Gaisler Research LEON3 SoC on the Xilinx Virtex-II Pro FPGA uses a Fixed Width Exponentiation (FWE) algorithm for certain signature calculations, and does not verify the signature before providing it to a caller, which makes it easier for physically proximate attackers to determine the private key via a modified supply voltage for the microprocessor, related to a "fault-based attack." | We are currently waiting for a fix from the vendor. |
| CVE-2019-9192 | Low | glibc | https://scout.docker.com/vulnerabilities/id/CVE-2019-9192 | 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 | We are currently waiting for a fix from the vendor. |
| CVE-2019-1010025 | Low | glibc | https://scout.docker.com/vulnerabilities/id/CVE-2019-1010025 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2019-1010024 | Low | glibc | https://scout.docker.com/vulnerabilities/id/CVE-2019-1010024 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2019-1010023 | Low | glibc | https://scout.docker.com/vulnerabilities/id/CVE-2019-1010023 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2019-1010022 | Low | glibc | https://scout.docker.com/vulnerabilities/id/CVE-2019-1010022 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2018-20796 | Low | glibc | https://scout.docker.com/v/CVE-2018-20796 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2010-4756 | Low | glibc | https://scout.docker.com/v/CVE-2010-4756 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2025-45582 | Medium | tar | https://scout.docker.com/v/CVE-2025-45582 | GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory. | We are currently waiting for a fix from the vendor. |
| CVE-2005-2541 | Low | tar | https://scout.docker.com/v/CVE-2005-2541 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2023-31486 | Low | perl | https://scout.docker.com/v/CVE-2023-31486 | HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates. | We are currently waiting for a fix from the vendor. |
| CVE-2011-4116 | Low | perl | https://scout.docker.com/v/CVE-2011-4116 | _is_safe in the File::Temp module for Perl does not properly handle symlinks. | We are currently waiting for a fix from the vendor. |
| CVE-2022-0563 | Low | util-linux | https://scout.docker.com/v/CVE-2022-0563 | A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4. | We are currently waiting for a fix from the vendor. |
| CVE-2011-3374 | Low | apt | https://scout.docker.com/v/CVE-2011-3374 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2022-3219 | Low | gnupg2 | https://scout.docker.com/v/CVE-2022-3219 | GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB. | We are currently waiting for a fix from the vendor. |
| CVE-2025-5278 | Low | coreutils | https://scout.docker.com/v/CVE-2025-5278 | A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data. | We are currently waiting for a fix from the vendor. |
| CVE-2017-18018 | Low | coreutils | https://scout.docker.com/v/CVE-2017-18018 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2024-26461 | Low | krb5 | https://scout.docker.com/vulnerabilities/id/CVE-2024-26461 | Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c. | We are currently waiting for a fix from the vendor. |
| CVE-2024-26458 | Low | krb5 | https://scout.docker.com/vulnerabilities/id/CVE-2024-26458 | Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c. | We are currently waiting for a fix from the vendor. |
| CVE-2018-5709 | Low | krb5 | https://scout.docker.com/v/CVE-2018-5709 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2024-2236 | Low | libgcrypt | https://scout.docker.com/v/CVE-2024-2236 | A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts. | We are currently waiting for a fix from the vendor. |
| CVE-2018-6829 | Low | libgcrypt | https://scout.docker.com/v/CVE-2018-6829 | 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. | We are currently waiting for a fix from the vendor. |
| CVE-2022-27943 | Low | gcc | https://scout.docker.com/vulnerabilities/id/CVE-2022-27943 | libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new. | We are currently waiting for a fix from the vendor. |
| CVE-2025-0725 | Low | curl | https://scout.docker.com/v/CVE-2025-0725 | When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING option, using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. | We are currently waiting for a fix from the vendor. |
| CVE-2024-2379 | Low | curl | https://scout.docker.com/vulnerabilities/id/CVE-2024-2379 | libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems. | We are currently waiting for a fix from the vendor. |