OS | Resource | Resource Type | Installed Version | Vulnerability Name | Publish Date | Referenced By | NVD CVSS v3 Severity | Fix Version | Solution | Description
-- | -- | -- | -- | -- | -- | -- | -- | -- | -- | --
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22898 | 44358 | | low | | | curl 7.7 through 7.76.1 suffers from an information disclosure when the `-t` command line option, known as `CURLOPT_TELNETOPTIONS` in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22922 | 44413 | | medium | | | When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22923 | 44413 | | medium | | | When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22924 | 44413 | | low | | | libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths *case insensitively*,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22945 | 44462 | | critical | | | When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and also free it *again*.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22946 | 44468 | | high | | | A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL` or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations **withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22947 | 44468 | | medium | | | When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got *before* the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-22576 | 44707 | | high | | | An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only).
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27774 | 44714 | | medium | | | An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27775 | 44714 | | high | | | An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connection pool but with a different zone id it could reuse a connection instead.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27776 | 44714 | | medium | | | A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27781 | 44714 | | high | | | libcurl provides the `CURLOPT_CERTINFO` option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27782 | 44714 | | high | | | libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32205 | 44749 | | | | | A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on `foo.example.com` can set cookies that also would match for `bar.example.com`, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32206 | 44749 | | | | | curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32207 | 44749 | | | | | When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally *widen* the permissions for the target file, leaving the updated file accessible to more users than intended.
debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32208 | 44749 | | | | | When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client.
debian 11 | netty-codec-http | package | 4.1.72.Final | CVE-2022-24823 | 44687 | | medium | 4.1.77.Final | Upgrade package netty-codec-http to version 4.1.77.Final or above. | Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user.
debian 11 | protobuf-java | package | 3.19.1 | CVE-2021-22569 | 44571 | | medium | 3.19.2 | Upgrade package protobuf-java to version 3.19.2 or above. | An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions.
debian 11 | jackson-databind | package | 2.13.0 | CVE-2020-36518 | 44631 | | high | 2.13.2.1 | Upgrade package jackson-databind to version 2.13.2.1 or above. | jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.
debian 11 | handlebars.js | package | 4.7.6 | CVE-2021-23369 | 44298 | | critical | 4.7.7 | Upgrade package handlebars.js to version 4.7.7 or above. | The package handlebars before 4.7.7 are vulnerable to Remote Code Execution (RCE) when selecting certain compiling options to compile templates coming from an untrusted source.
debian 11 | handlebars.js | package | 4.7.6 | CVE-2021-23383 | 44320 | | critical | 4.7.7 | Upgrade package handlebars.js to version 4.7.7 or above. | The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source.
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2007-6755 | 41558 | | | | | The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE.
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2010-0928 | 40242 | | | | | 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."
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2021-4160 | 44589 | DSA-5103-1 | medium | 1.1.1k-1+deb11u2 | Upgrade package openssl to version 1.1.1k-1+deb11u2 or above. | There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-dev (Affected 1.0.2-1.0.2zb).
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-0778 | 44635 | DSA-5103-1 | high | 1.1.1k-1+deb11u2 | Upgrade package openssl to version 1.1.1k-1+deb11u2 or above. | The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc).
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-1292 | 44684 | DSA-5139-1 | critical | 1.1.1n-0+deb11u2 | Upgrade package openssl to version 1.1.1n-0+deb11u2 or above. | The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-2068 | 44733 | DSA-5169-1 | critical | 1.1.1n-0+deb11u3 | Upgrade package openssl to version 1.1.1n-0+deb11u3 or above. | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-2097 | 44747 | | | | | AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p).
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | DSA-5103-1 | 44635 | | high | 1.1.1k-1+deb11u2 | Upgrade package openssl to version 1.1.1k-1+deb11u2 or above.
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | DSA-5139-1 | 44698 | | critical | 1.1.1n-0+deb11u2 | Upgrade package openssl to version 1.1.1n-0+deb11u2 or above.
debian 11 | openssl | package | 1.1.1k-1+deb11u1 | DSA-5169-1 | 44738 | | critical | 1.1.1n-0+deb11u3 | Upgrade package openssl to version 1.1.1n-0+deb11u3 or above.
debian 11 | util-linux | package | 2.36.1-8 | CVE-2021-3995 | | DSA-5055-1 | 2.36.1-8+deb11u1 | Upgrade package util-linux to version 2.36.1-8+deb11u1 or above.
debian 11 | util-linux | package | 2.36.1-8 | CVE-2021-3996 | | DSA-5055-1 | 2.36.1-8+deb11u1 | Upgrade package util-linux to version 2.36.1-8+deb11u1 or above.
debian 11 | util-linux | package | 2.36.1-8 | CVE-2022-0563 | 44613 | | medium | | | 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.
debian 11 | util-linux | package | 2.36.1-8 | DSA-5055-1 | 44585 | | | 2.36.1-8+deb11u1 | Upgrade package util-linux to version 2.36.1-8+deb11u1 or above.
debian 11 | tar | package | 1.34+dfsg-1 | CVE-2005-2541 | 38574 | | | | | 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.
debian 11 | libgcrypt20 | package | 1.8.7-6 | CVE-2018-6829 | 43138 | | high | | | 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.
debian 11 | libgcrypt20 | package | 1.8.7-6 | CVE-2021-33560 | 44355 | | high | | | Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP.
debian 11 | gzip | package | 1.10-4 | CVE-2022-1271 | 44658 | DSA-5122-1 | medium | 1.10-4+deb11u1 | Upgrade package gzip to version 1.10-4+deb11u1 or above. | This bug was introduced in gzip-1.3.10 and is relatively hard to exploit
debian 11 | gzip | package | 1.10-4 | DSA-5122-1 | 44669 | | medium | 1.10-4+deb11u1 | Upgrade package gzip to version 1.10-4+deb11u1 or above.
debian 11 | e2fsprogs | package | 1.46.2-2 | CVE-2022-1304 | 44665 | | high | | | An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem.
debian 11 | dpkg | package | 1.20.9 | CVE-2022-1664 | 44707 | DSA-5147-1 | critical | 1.20.10 | Upgrade package dpkg to version 1.20.10 or above. | Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs.
debian 11 | dpkg | package | 1.20.9 | DSA-5147-1 | 44706 | | critical | 1.20.10 | Upgrade package dpkg to version 1.20.10 or above.
debian 11 | coreutils | package | 8.32-4+b1 | CVE-2017-18018 | 43104 | | medium | | | 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.
debian 11 | apt | package | 2.2.4 | CVE-2011-3374 | 43795 | | low | | | 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.
aqua sec scan results for the docker image i guess handlebars.js one is from frontend
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns="http://www.w3.org/TR/REC-html40">
OS | Resource | Resource Type | Installed Version | Vulnerability Name | Publish Date | Referenced By | NVD CVSS v3 Severity | Fix Version | Solution | Description -- | -- | -- | -- | -- | -- | -- | -- | -- | -- | -- debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22898 | 44358 | | low | | | curl 7.7 through 7.76.1 suffers from an information disclosure when the `-t` command line option, known as `CURLOPT_TELNETOPTIONS` in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22922 | 44413 | | medium | | | When curl is instructed to download content using the metalink feature, thecontents is verified against a hash provided in the metalink XML file.The metalink XML file points out to the client how to get the same contentfrom a set of different URLs, potentially hosted by different servers and theclient can then download the file from one or several of them. In a serial orparallel manner.If one of the servers hosting the contents has been breached and the contentsof the specific file on that server is replaced with a modified payload, curlshould detect this when the hash of the file mismatches after a completeddownload. It should remove the contents and instead try getting the contentsfrom another URL. This is not done, and instead such a hash mismatch is onlymentioned in text and the potentially malicious content is kept in the file ondisk. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22923 | 44413 | | medium | | | When curl is instructed to get content using the metalink feature, and a user name and password are used to download the metalink XML file, those same credentials are then subsequently passed on to each of the servers from which curl will download or try to download the contents from. Often contrary to the user's expectations and intentions and without telling the user it happened. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22924 | 44413 | | low | | | libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths *case insensitively*,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22945 | 44462 | | critical | | | When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and also free it *again*. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22946 | 44468 | | high | | | A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL` or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations **withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2021-22947 | 44468 | | medium | | | When curl >= 7.20.0 and <= 7.78.0 connects to an IMAP or POP3 server to retrieve data using STARTTLS to upgrade to TLS security, the server can respond and send back multiple responses at once that curl caches. curl would then upgrade to TLS but not flush the in-queue of cached responses but instead continue using and trustingthe responses it got *before* the TLS handshake as if they were authenticated.Using this flaw, it allows a Man-In-The-Middle attacker to first inject the fake responses, then pass-through the TLS traffic from the legitimate server and trick curl into sending data back to the user thinking the attacker's injected data comes from the TLS-protected server. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-22576 | 44707 | | high | | | An improper authentication vulnerability exists in curl 7.33.0 to and including 7.82.0 which might allow reuse OAUTH2-authenticated connections without properly making sure that the connection was authenticated with the same credentials as set for this transfer. This affects SASL-enabled protocols: SMPTP(S), IMAP(S), POP3(S) and LDAP(S) (openldap only). debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27774 | 44714 | | medium | | | An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27775 | 44714 | | high | | | An information disclosure vulnerability exists in curl 7.65.0 to 7.82.0 are vulnerable that by using an IPv6 address that was in the connection pool but with a different zone id it could reuse a connection instead. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27776 | 44714 | | medium | | | A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27781 | 44714 | | high | | | libcurl provides the `CURLOPT_CERTINFO` option to allow applications torequest details to be returned about a server's certificate chain.Due to an erroneous function, a malicious server could make libcurl built withNSS get stuck in a never-ending busy-loop when trying to retrieve thatinformation. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-27782 | 44714 | | high | | | libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32205 | 44749 | | | | | A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on `foo.example.com` can set cookies that also would match for `bar.example.com`, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32206 | 44749 | | | | | curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32207 | 44749 | | | | | When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the operation with a rename from a temporary name to the final target file name.In that rename operation, it might accidentally *widen* the permissions for the target file, leaving the updated file accessible to more users than intended. debian 11 | curl | package | 7.74.0-1.3+deb11u1 | CVE-2022-32208 | 44749 | | | | | When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client. debian 11 | netty-codec-http | package | 4.1.72.Final | CVE-2022-24823 | 44687 | | medium | 4.1.77.Final | Upgrade package netty-codec-http to version 4.1.77.Final or above. | Netty is an open-source, asynchronous event-driven network application framework. The package `io.netty:netty-codec-http` prior to version 4.1.77.Final contains an insufficient fix for CVE-2021-21290. When Netty's multipart decoders are used local information disclosure can occur via the local system temporary directory if temporary storing uploads on the disk is enabled. This only impacts applications running on Java version 6 and lower. Additionally, this vulnerability impacts code running on Unix-like systems, and very old versions of Mac OSX and Windows as they all share the system temporary directory between all users. Version 4.1.77.Final contains a patch for this vulnerability. As a workaround, specify one's own `java.io.tmpdir` when starting the JVM or use DefaultHttpDataFactory.setBaseDir(...) to set the directory to something that is only readable by the current user. debian 11 | protobuf-java | package | 3.19.1 | CVE-2021-22569 | 44571 | | medium | 3.19.2 | Upgrade package protobuf-java to version 3.19.2 or above. | An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions. debian 11 | jackson-databind | package | 2.13.0 | CVE-2020-36518 | 44631 | | high | 2.13.2.1 | Upgrade package jackson-databind to version 2.13.2.1 or above. | jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects. debian 11 | handlebars.js | package | 4.7.6 | CVE-2021-23369 | 44298 | | critical | 4.7.7 | Upgrade package handlebars.js to version 4.7.7 or above. | The package handlebars before 4.7.7 are vulnerable to Remote Code Execution (RCE) when selecting certain compiling options to compile templates coming from an untrusted source. debian 11 | handlebars.js | package | 4.7.6 | CVE-2021-23383 | 44320 | | critical | 4.7.7 | Upgrade package handlebars.js to version 4.7.7 or above. | The package handlebars before 4.7.7 are vulnerable to Prototype Pollution when selecting certain compiling options to compile templates coming from an untrusted source. debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2007-6755 | 41558 | | | | | The NIST SP 800-90A default statement of the Dual Elliptic Curve Deterministic Random Bit Generation (Dual_EC_DRBG) algorithm contains point Q constants with a possible relationship to certain "skeleton key" values, which might allow context-dependent attackers to defeat cryptographic protection mechanisms by leveraging knowledge of those values. NOTE: this is a preliminary CVE for Dual_EC_DRBG; future research may provide additional details about point Q and associated attacks, and could potentially lead to a RECAST or REJECT of this CVE. debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2010-0928 | 40242 | | | | | 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." debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2021-4160 | 44589 | DSA-5103-1 | medium | 1.1.1k-1+deb11u2 | Upgrade package openssl to version 1.1.1k-1+deb11u2 or above. | There is a carry propagation bug in the MIPS32 and MIPS64 squaring procedure. Many EC algorithms are affected, including some of the TLS 1.3 default curves. Impact was not analyzed in detail, because the pre-requisites for attack are considered unlikely and include reusing private keys. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be significant. However, for an attack on TLS to be meaningful, the server would have to share the DH private key among multiple clients, which is no longer an option since CVE-2016-0701. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0.0. It was addressed in the releases of 1.1.1m and 3.0.1 on the 15th of December 2021. For the 1.0.2 release it is addressed in git commit 6fc1aaaf3 that is available to premium support customers only. It will be made available in 1.0.2zc when it is released. The issue only affects OpenSSL on MIPS platforms. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). Fixed in OpenSSL 1.1.1m (Affected 1.1.1-1.1.1l). Fixed in OpenSSL 1.0.2zc-dev (Affected 1.0.2-1.0.2zb). debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-0778 | 44635 | DSA-5103-1 | high | 1.1.1k-1+deb11u2 | Upgrade package openssl to version 1.1.1k-1+deb11u2 or above. | The BN_mod_sqrt() function, which computes a modular square root, contains a bug that can cause it to loop forever for non-prime moduli. Internally this function is used when parsing certificates that contain elliptic curve public keys in compressed form or explicit elliptic curve parameters with a base point encoded in compressed form. It is possible to trigger the infinite loop by crafting a certificate that has invalid explicit curve parameters. Since certificate parsing happens prior to verification of the certificate signature, any process that parses an externally supplied certificate may thus be subject to a denial of service attack. The infinite loop can also be reached when parsing crafted private keys as they can contain explicit elliptic curve parameters. Thus vulnerable situations include: - TLS clients consuming server certificates - TLS servers consuming client certificates - Hosting providers taking certificates or private keys from customers - Certificate authorities parsing certification requests from subscribers - Anything else which parses ASN.1 elliptic curve parameters Also any other applications that use the BN_mod_sqrt() where the attacker can control the parameter values are vulnerable to this DoS issue. In the OpenSSL 1.0.2 version the public key is not parsed during initial parsing of the certificate which makes it slightly harder to trigger the infinite loop. However any operation which requires the public key from the certificate will trigger the infinite loop. In particular the attacker can use a self-signed certificate to trigger the loop during verification of the certificate signature. This issue affects OpenSSL versions 1.0.2, 1.1.1 and 3.0. It was addressed in the releases of 1.1.1n and 3.0.2 on the 15th March 2022. Fixed in OpenSSL 3.0.2 (Affected 3.0.0,3.0.1). Fixed in OpenSSL 1.1.1n (Affected 1.1.1-1.1.1m). Fixed in OpenSSL 1.0.2zd (Affected 1.0.2-1.0.2zc). debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-1292 | 44684 | DSA-5139-1 | critical | 1.1.1n-0+deb11u2 | Upgrade package openssl to version 1.1.1n-0+deb11u2 or above. | The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd). debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-2068 | 44733 | DSA-5169-1 | critical | 1.1.1n-0+deb11u3 | Upgrade package openssl to version 1.1.1n-0+deb11u3 or above. | In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze). debian 11 | openssl | package | 1.1.1k-1+deb11u1 | CVE-2022-2097 | 44747 | | | | | AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. This could reveal sixteen bytes of data that was preexisting in the memory that wasn't written. In the special case of "in place" encryption, sixteen bytes of the plaintext would be revealed. Since OpenSSL does not support OCB based cipher suites for TLS and DTLS, they are both unaffected. Fixed in OpenSSL 3.0.5 (Affected 3.0.0-3.0.4). Fixed in OpenSSL 1.1.1q (Affected 1.1.1-1.1.1p). debian 11 | openssl | package | 1.1.1k-1+deb11u1 | DSA-5103-1 | 44635 | | high | 1.1.1k-1+deb11u2 | Upgrade package openssl to version 1.1.1k-1+deb11u2 or above. debian 11 | openssl | package | 1.1.1k-1+deb11u1 | DSA-5139-1 | 44698 | | critical | 1.1.1n-0+deb11u2 | Upgrade package openssl to version 1.1.1n-0+deb11u2 or above. debian 11 | openssl | package | 1.1.1k-1+deb11u1 | DSA-5169-1 | 44738 | | critical | 1.1.1n-0+deb11u3 | Upgrade package openssl to version 1.1.1n-0+deb11u3 or above. debian 11 | util-linux | package | 2.36.1-8 | CVE-2021-3995 | | DSA-5055-1 | 2.36.1-8+deb11u1 | Upgrade package util-linux to version 2.36.1-8+deb11u1 or above. debian 11 | util-linux | package | 2.36.1-8 | CVE-2021-3996 | | DSA-5055-1 | 2.36.1-8+deb11u1 | Upgrade package util-linux to version 2.36.1-8+deb11u1 or above. debian 11 | util-linux | package | 2.36.1-8 | CVE-2022-0563 | 44613 | | medium | | | 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. debian 11 | util-linux | package | 2.36.1-8 | DSA-5055-1 | 44585 | | | 2.36.1-8+deb11u1 | Upgrade package util-linux to version 2.36.1-8+deb11u1 or above. debian 11 | tar | package | 1.34+dfsg-1 | CVE-2005-2541 | 38574 | | | | | 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. debian 11 | libgcrypt20 | package | 1.8.7-6 | CVE-2018-6829 | 43138 | | high | | | 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. debian 11 | libgcrypt20 | package | 1.8.7-6 | CVE-2021-33560 | 44355 | | high | | | Libgcrypt before 1.8.8 and 1.9.x before 1.9.3 mishandles ElGamal encryption because it lacks exponent blinding to address a side-channel attack against mpi_powm, and the window size is not chosen appropriately. This, for example, affects use of ElGamal in OpenPGP. debian 11 | gzip | package | 1.10-4 | CVE-2022-1271 | 44658 | DSA-5122-1 | medium | 1.10-4+deb11u1 | Upgrade package gzip to version 1.10-4+deb11u1 or above. | This bug was introduced in gzip-1.3.10 and is relatively hard to exploit debian 11 | gzip | package | 1.10-4 | DSA-5122-1 | 44669 | | medium | 1.10-4+deb11u1 | Upgrade package gzip to version 1.10-4+deb11u1 or above. debian 11 | e2fsprogs | package | 1.46.2-2 | CVE-2022-1304 | 44665 | | high | | | An out-of-bounds read/write vulnerability was found in e2fsprogs 1.46.5. This issue leads to a segmentation fault and possibly arbitrary code execution via a specially crafted filesystem. debian 11 | dpkg | package | 1.20.9 | CVE-2022-1664 | 44707 | DSA-5147-1 | critical | 1.20.10 | Upgrade package dpkg to version 1.20.10 or above. | Dpkg::Source::Archive in dpkg, the Debian package management system, before version 1.21.8, 1.20.10, 1.19.8, 1.18.26 is prone to a directory traversal vulnerability. When extracting untrusted source packages in v2 and v3 source package formats that include a debian.tar, the in-place extraction can lead to directory traversal situations on specially crafted orig.tar and debian.tar tarballs. debian 11 | dpkg | package | 1.20.9 | DSA-5147-1 | 44706 | | critical | 1.20.10 | Upgrade package dpkg to version 1.20.10 or above. debian 11 | coreutils | package | 8.32-4+b1 | CVE-2017-18018 | 43104 | | medium | | | 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. debian 11 | apt | package | 2.2.4 | CVE-2011-3374 | 43795 | | low | | | 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.