Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1
Description:  OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

CVE ID: CVE-2018-0735
Severity:  Negligible
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

CVE ID: CVE-2019-1563
Severity:  Unknown
Fixed in Version:  1.1.1d-0+deb10u1
Description:  In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2018-0734
Severity:  Unknown
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1
Description:  OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1547
Severity:  Low
Fixed in Version:  1.1.1d-0+deb10u1
Description:  Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2020-1967
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u3
Description:  Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

CVE ID: CVE-2020-1967
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u3
Description:  Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

CVE ID: CVE-2018-0735
Severity:  Negligible
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

CVE ID: CVE-2019-1547
Severity:  Low
Fixed in Version:  1.1.1d-0+deb10u1
Description:  Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2020-1967
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u3
Description:  Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

CVE ID: CVE-2019-1563
Severity:  Medium
Fixed in Version:  1.1.1d-0+deb10u1
Description:  In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2020-1967
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u3
Description:  Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1
Description:  OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1563
Severity:  Medium
Fixed in Version:  1.1.1d-0+deb10u1
Description:  In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2018-0735
Severity:  Negligible
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

CVE ID: CVE-2018-0734
Severity:  Unknown
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

CVE ID: CVE-2019-1563
Severity:  Medium
Fixed in Version:  1.1.1d-0+deb10u1
Description:  In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

Package Name:  procps  Version :  2:3.3.12-3ubuntu1.2

 Vulnerabilities

CVE ID: CVE-2018-1126
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1122
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1122
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1123
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1126
Severity:  High
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1125
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1126
Severity:  High
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1122
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1124
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1123
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1125
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1123
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1126
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1125
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1124
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1124
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1123
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1125
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1125
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1124
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1123
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1124
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1122
Severity:  Medium
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1122
Severity:  Unknown
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1126
Severity:  High
Fixed in Version:  2:3.3.15-1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

Package Name:  curl  Version :  7.58.0-2ubuntu3.10

 Vulnerabilities

CVE ID: CVE-2018-16840
Severity:  Negligible
Fixed in Version:  7.62.0-1
Description:  A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

CVE ID: CVE-2019-5482
Severity:  High
Fixed in Version:  7.64.0-4+deb10u1
Description:  Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

CVE ID: CVE-2018-14618
Severity:  Critical
Fixed in Version:  7.62.0-1
Description:  curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

CVE ID: CVE-2019-5481
Severity:  Unknown
Fixed in Version:  7.64.0-4+deb10u1
Description:  Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

CVE ID: CVE-2018-1000300
Severity:  Negligible
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

CVE ID: CVE-2018-16842
Severity:  Unknown
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

CVE ID: CVE-2019-3822
Severity:  High
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

CVE ID: CVE-2018-16840
Severity:  Negligible
Fixed in Version:  7.62.0-1
Description:  A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

CVE ID: CVE-2018-16842
Severity:  Medium
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

CVE ID: CVE-2018-1000301
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

CVE ID: CVE-2018-1000120
Severity:  High
Fixed in Version:  7.60.0-1
Description:  A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

CVE ID: CVE-2019-3822
Severity:  Unknown
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

CVE ID: CVE-2018-1000121
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

CVE ID: CVE-2018-16839
Severity:  Unknown
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

CVE ID: CVE-2018-1000300
Severity:  Negligible
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

CVE ID: CVE-2018-1000301
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

CVE ID: CVE-2019-5436
Severity:  Medium
Fixed in Version:  7.64.0-4
Description:  A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

CVE ID: CVE-2018-14618
Severity:  Critical
Fixed in Version:  7.62.0-1
Description:  curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

CVE ID: CVE-2018-1000121
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

CVE ID: CVE-2018-14618
Severity:  Unknown
Fixed in Version:  7.62.0-1
Description:  curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

CVE ID: CVE-2018-0500
Severity:  Negligible
Fixed in Version:  7.61.0-1
Description:  Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

CVE ID: CVE-2018-16839
Severity:  High
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

CVE ID: CVE-2019-5481
Severity:  High
Fixed in Version:  7.64.0-4+deb10u1
Description:  Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

CVE ID: CVE-2019-5436
Severity:  Unknown
Fixed in Version:  7.64.0-4
Description:  A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

CVE ID: CVE-2018-1000301
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

CVE ID: CVE-2019-5482
Severity:  Unknown
Fixed in Version:  7.64.0-4+deb10u1
Description:  Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

CVE ID: CVE-2018-16839
Severity:  High
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

CVE ID: CVE-2018-1000120
Severity:  High
Fixed in Version:  7.60.0-1
Description:  A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

CVE ID: CVE-2018-1000300
Severity:  Negligible
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

CVE ID: CVE-2018-1000122
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

CVE ID: CVE-2018-16839
Severity:  High
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

CVE ID: CVE-2019-5481
Severity:  High
Fixed in Version:  7.64.0-4+deb10u1
Description:  Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

CVE ID: CVE-2019-5435
Severity:  Negligible
Fixed in Version:  7.64.0-4
Description:  An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

CVE ID: CVE-2019-5481
Severity:  High
Fixed in Version:  7.64.0-4+deb10u1
Description:  Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

CVE ID: CVE-2018-1000120
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

CVE ID: CVE-2018-16890
Severity:  Medium
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

CVE ID: CVE-2018-1000300
Severity:  Negligible
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

CVE ID: CVE-2018-16842
Severity:  Medium
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

CVE ID: CVE-2018-0500
Severity:  Negligible
Fixed in Version:  7.61.0-1
Description:  Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

CVE ID: CVE-2018-1000300
Severity:  Negligible
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.54.1 to and including curl 7.59.0 contains a CWE-122: Heap-based Buffer Overflow vulnerability in denial of service and more that can result in curl might overflow a heap based memory buffer when closing down an FTP connection with very long server command replies.. This vulnerability appears to have been fixed in curl < 7.54.1 and curl >= 7.60.0.

CVE ID: CVE-2018-1000122
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

CVE ID: CVE-2018-16890
Severity:  Unknown
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

CVE ID: CVE-2018-16840
Severity:  Negligible
Fixed in Version:  7.62.0-1
Description:  A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

CVE ID: CVE-2018-16840
Severity:  Negligible
Fixed in Version:  7.62.0-1
Description:  A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

CVE ID: CVE-2018-14618
Severity:  Unknown
Fixed in Version:  7.62.0-1
Description:  curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

CVE ID: CVE-2019-5482
Severity:  High
Fixed in Version:  7.64.0-4+deb10u1
Description:  Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

CVE ID: CVE-2019-3822
Severity:  Unknown
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

CVE ID: CVE-2019-3822
Severity:  High
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

CVE ID: CVE-2018-1000122
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

CVE ID: CVE-2018-1000301
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

CVE ID: CVE-2018-1000122
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

CVE ID: CVE-2019-3822
Severity:  High
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 are vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.

CVE ID: CVE-2019-3823
Severity:  Medium
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

CVE ID: CVE-2018-16890
Severity:  Medium
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

CVE ID: CVE-2018-0500
Severity:  Negligible
Fixed in Version:  7.61.0-1
Description:  Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

CVE ID: CVE-2018-16842
Severity:  Medium
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

CVE ID: CVE-2019-5482
Severity:  Unknown
Fixed in Version:  7.64.0-4+deb10u1
Description:  Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

CVE ID: CVE-2019-5482
Severity:  High
Fixed in Version:  7.64.0-4+deb10u1
Description:  Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.

CVE ID: CVE-2018-1000122
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage

CVE ID: CVE-2019-3823
Severity:  Unknown
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

CVE ID: CVE-2019-3823
Severity:  Unknown
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

CVE ID: CVE-2019-5436
Severity:  Medium
Fixed in Version:  7.64.0-4
Description:  A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

CVE ID: CVE-2018-16839
Severity:  Unknown
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.

CVE ID: CVE-2018-1000120
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

CVE ID: CVE-2018-1000121
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

CVE ID: CVE-2018-16840
Severity:  Negligible
Fixed in Version:  7.62.0-1
Description:  A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the Curl_close() function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.

CVE ID: CVE-2018-1000121
Severity:  Medium
Fixed in Version:  7.60.0-1
Description:  A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

CVE ID: CVE-2018-16890
Severity:  Unknown
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

CVE ID: CVE-2019-5481
Severity:  Unknown
Fixed in Version:  7.64.0-4+deb10u1
Description:  Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

CVE ID: CVE-2019-5435
Severity:  Negligible
Fixed in Version:  7.64.0-4
Description:  An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

CVE ID: CVE-2019-3823
Severity:  Medium
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

CVE ID: CVE-2019-5435
Severity:  Negligible
Fixed in Version:  7.64.0-4
Description:  An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

CVE ID: CVE-2019-5436
Severity:  Unknown
Fixed in Version:  7.64.0-4
Description:  A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

CVE ID: CVE-2018-1000120
Severity:  High
Fixed in Version:  7.60.0-1
Description:  A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse.

CVE ID: CVE-2019-5435
Severity:  Negligible
Fixed in Version:  7.64.0-4
Description:  An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

CVE ID: CVE-2019-3823
Severity:  Medium
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.34.0 to before 7.64.0 are vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to smtp_endofresp() isn't NUL terminated and contains no character ending the parsed number, and len is set to 5, then the strtol() call reads beyond the allocated buffer. The read contents will not be returned to the caller.

CVE ID: CVE-2019-5436
Severity:  Medium
Fixed in Version:  7.64.0-4
Description:  A heap buffer overflow in the TFTP receiving code allows for DoS or arbitrary code execution in libcurl versions 7.19.4 through 7.64.1.

CVE ID: CVE-2018-14618
Severity:  Critical
Fixed in Version:  7.62.0-1
Description:  curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.)

CVE ID: CVE-2018-16842
Severity:  Unknown
Fixed in Version:  7.62.0-1
Description:  Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.

CVE ID: CVE-2018-0500
Severity:  Negligible
Fixed in Version:  7.61.0-1
Description:  Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

CVE ID: CVE-2018-1000121
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  A NULL pointer dereference exists in curl 7.21.0 to and including curl 7.58.0 in the LDAP code that allows an attacker to cause a denial of service

CVE ID: CVE-2019-5435
Severity:  Negligible
Fixed in Version:  7.64.0-4
Description:  An integer overflow in curl's URL API results in a buffer overflow in libcurl 7.62.0 to and including 7.64.1.

CVE ID: CVE-2018-1000301
Severity:  Unknown
Fixed in Version:  7.60.0-1
Description:  curl version curl 7.20.0 to and including curl 7.59.0 contains a CWE-126: Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded RTSP content.. This vulnerability appears to have been fixed in curl < 7.20.0 and curl >= 7.60.0.

CVE ID: CVE-2018-0500
Severity:  Negligible
Fixed in Version:  7.61.0-1
Description:  Curl_smtp_escape_eob in lib/smtp.c in curl 7.54.1 to and including curl 7.60.0 has a heap-based buffer overflow that might be exploitable by an attacker who can control the data that curl transmits over SMTP with certain settings (i.e., use of a nonstandard --limit-rate argument or CURLOPT_BUFFERSIZE value).

CVE ID: CVE-2018-16890
Severity:  Medium
Fixed in Version:  7.64.0-1
Description:  libcurl versions from 7.36.0 to before 7.64.0 is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (lib/vauth/ntlm.c:ntlm_decode_type2_target) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.

 :x: Manifest File: Dockerfile-docker.io/library/node:12.16.1-alpine

Vulnerability Data by Clair
Package Name:  wget  Version :  1.19.4-1ubuntu2.2

 Vulnerabilities

CVE ID: CVE-2018-0494
Severity:  Medium
Fixed in Version:  1.19.5-r0
Description:

CVE ID: CVE-2019-5953
Severity:  High
Fixed in Version:  1.20.3-r0
Description:

CVE ID: CVE-2018-20483
Severity:  Low
Fixed in Version:  1.20.1-r0
Description:

Package Name:  e2fsprogs  Version :  1.44.1-1ubuntu1.3

 Vulnerabilities

CVE ID: CVE-2019-5188
Severity:  Medium
Fixed in Version:  1.45.5-r0
Description:

CVE ID: CVE-2019-5094
Severity:  Medium
Fixed in Version:  1.45.4-r0
Description:

Package Name:  unzip  Version :  6.0-21ubuntu1

 Vulnerabilities

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-r3
Description:

CVE ID: CVE-2014-8140
Severity:  Medium
Fixed in Version:  6.0-r3
Description:

CVE ID: CVE-2016-9844
Severity:  Low
Fixed in Version:  6.0-r3
Description:

CVE ID: CVE-2014-8141
Severity:  Medium
Fixed in Version:  6.0-r3
Description:

CVE ID: CVE-2014-8139
Severity:  Medium
Fixed in Version:  6.0-r3
Description:

CVE ID: CVE-2015-7697
Severity:  Medium
Fixed in Version:  6.0-r1
Description:

CVE ID: CVE-2014-9913
Severity:  Low
Fixed in Version:  6.0-r3
Description:

CVE ID: CVE-2015-7696
Severity:  Medium
Fixed in Version:  6.0-r1
Description:

CVE ID: CVE-2014-9636
Severity:  Medium
Fixed in Version:  6.0-r3
Description:

Package Name:  tar  Version :  1.29b-2ubuntu0.1

 Vulnerabilities

CVE ID: CVE-2018-20482
Severity:  Low
Fixed in Version:  1.31-r0
Description:

CVE ID: CVE-2016-6321
Severity:  Medium
Fixed in Version:  1.29-r1
Description:

Package Name:  bzip2  Version :  1.0.6-8.1ubuntu0.2

 Vulnerabilities

CVE ID: CVE-2019-12900
Severity:  High
Fixed in Version:  1.0.6-r7
Description:

CVE ID: CVE-2016-3189
Severity:  Medium
Fixed in Version:  1.0.6-r5
Description:

Package Name:  openssl  Version :  1.1.1-1ubuntu2.1~18.04.6

 Vulnerabilities

CVE ID: CVE-2019-1551
Severity:  Medium
Fixed in Version:  1.1.1d-r3
Description:

CVE ID: CVE-2019-1563
Severity:  Medium
Fixed in Version:  1.1.1d-r1
Description:

CVE ID: CVE-2018-0735
Severity:  Medium
Fixed in Version:  1.1.1a-r0
Description:

CVE ID: CVE-2019-1547
Severity:  Low
Fixed in Version:  1.1.1d-r1
Description:

CVE ID: CVE-2019-1543
Severity:  Medium
Fixed in Version:  1.1.1b-r1
Description:

CVE ID: CVE-2018-0734
Severity:  Medium
Fixed in Version:  1.1.1a-r0
Description:

CVE ID: CVE-2019-1549
Severity:  Medium
Fixed in Version:  1.1.1d-r1
Description:

Package Name:  curl  Version :  7.58.0-2ubuntu3.10

 Vulnerabilities

CVE ID: CVE-2018-16842
Severity:  Medium
Fixed in Version:  7.62.0-r0
Description:

CVE ID: CVE-2018-16840
Severity:  High
Fixed in Version:  7.62.0-r0
Description:

CVE ID: CVE-2018-1000122
Severity:  Medium
Fixed in Version:  7.59.0-r0
Description:

CVE ID: CVE-2018-1000120
Severity:  High
Fixed in Version:  7.59.0-r0
Description:

CVE ID: CVE-2018-1000121
Severity:  Medium
Fixed in Version:  7.59.0-r0
Description:

CVE ID: CVE-2019-5436
Severity:  Medium
Fixed in Version:  7.65.0-r0
Description:

CVE ID: CVE-2019-3822
Severity:  High
Fixed in Version:  7.64.0-r0
Description:

CVE ID: CVE-2018-14618
Severity:  Critical
Fixed in Version:  7.61.1-r0
Description:

CVE ID: CVE-2018-16839
Severity:  High
Fixed in Version:  7.62.0-r0
Description:

CVE ID: CVE-2019-3823
Severity:  Medium
Fixed in Version:  7.64.0-r0
Description:

CVE ID: CVE-2019-5482
Severity:  High
Fixed in Version:  7.66.0-r0
Description:

CVE ID: CVE-2019-5435
Severity:  Medium
Fixed in Version:  7.65.0-r0
Description:

CVE ID: CVE-2018-1000301
Severity:  Medium
Fixed in Version:  7.60.0-r0
Description:

CVE ID: CVE-2018-0500
Severity:  High
Fixed in Version:  7.61.0-r0
Description:

CVE ID: CVE-2019-5481
Severity:  High
Fixed in Version:  7.66.0-r0
Description:

CVE ID: CVE-2018-1000300
Severity:  High
Fixed in Version:  7.60.0-r0
Description:

CVE ID: CVE-2018-16890
Severity:  Medium
Fixed in Version:  7.64.0-r0
Description:

Package Name:  coreutils  Version :  8.28-1ubuntu1

 Vulnerabilities

CVE ID: CVE-2017-18018
Severity:  Low
Fixed in Version:  8.30-r0
Description:

 :x: Manifest File: bank-knative-service/Dockerfile-node:12-slim

Vulnerability Data by Clair
Package Name:  unzip  Version :  6.0-21ubuntu1

 Vulnerabilities

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-21+deb9u2
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-21+deb9u2
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-21+deb9u2
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2018-1000035
Severity:  Unknown
Fixed in Version:  6.0-21+deb9u1
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-21+deb9u2
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-21+deb9u1
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-21+deb9u1
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-21+deb9u1
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-21+deb9u2
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2018-1000035
Severity:  Unknown
Fixed in Version:  6.0-21+deb9u1
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

Package Name:  procps  Version :  2:3.3.12-3ubuntu1.2

 Vulnerabilities

CVE ID: CVE-2018-1124
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1125
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1126
Severity:  High
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1123
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1124
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1124
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1125
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1123
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1126
Severity:  High
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1124
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1126
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1125
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1123
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1123
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1122
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1123
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a denial of service in ps via mmap buffer overflow. Inbuilt protection in ps maps a guard page at the end of the overflowed buffer, ensuring that the impact of this flaw is limited to a crash (temporary denial of service).

CVE ID: CVE-2018-1125
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1122
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1124
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to multiple integer overflows leading to a heap corruption in file2strvec function. This allows a privilege escalation for a local attacker who can create entries in procfs by starting processes, which could result in crashes or arbitrary code execution in proc utilities run by other users.

CVE ID: CVE-2018-1125
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a stack buffer overflow in pgrep. This vulnerability is mitigated by FORTIFY, as it involves strncat() to a stack-allocated string. When pgrep is compiled with FORTIFY (as on Red Hat Enterprise Linux and Fedora), the impact is limited to a crash.

CVE ID: CVE-2018-1126
Severity:  High
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1122
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1122
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

CVE ID: CVE-2018-1126
Severity:  Unknown
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to an incorrect integer size in proc/alloc.* leading to truncation/integer overflow issues. This flaw is related to CVE-2018-1124.

CVE ID: CVE-2018-1122
Severity:  Medium
Fixed in Version:  2:3.3.12-3+deb9u1
Description:  procps-ng before version 3.3.15 is vulnerable to a local privilege escalation in top. If a user runs top with HOME unset in an attacker-controlled directory, the attacker could achieve privilege escalation by exploiting one of several vulnerabilities in the config_file() function.

 :x: Manifest File: bank-user-cleanup-utility/pom.xml

Vulnerability Data by Snyk
Package Name:  org.postgresql:postgresql  Version :  42.2.10

 Vulnerabilities

CVE ID: CVE-2020-13692
Severity:  high
Fixed in Version:  42.2.13
Description:  org.postgresql:postgresql is a Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database. Affected versions of this package are vulnerable to XML External Entity (XXE) Injection. The PgSQLXML class used for parsing was found to allow external entities and multiple doc types which could allow XXE attacks.

Package Name:  org.apache.httpcomponents:httpclient  Version :  4.5.10

 Vulnerabilities

CVE ID: CVE-2020-13956
Severity:  medium
Fixed in Version:  4.5.13
Description:  org.apache.httpcomponents:httpclient is a HttpClient component of the Apache HttpComponents project. Affected versions of this package are vulnerable to Improper Input Validation. A malformed authority component in request URIs passed to the library as java.net.URI object will result in picking the wrong target host for request execution.

 :x: Manifest File: package-lock.json

Vulnerability Data by Snyk
Package Name:  ajv  Version :  6.12.0

 Vulnerabilities

CVE ID: CVE-2020-15366
Severity:  high
Fixed in Version:  6.12.3
Description:  ajv is an Another JSON Schema Validator Affected versions of this package are vulnerable to Prototype Pollution. A carefully crafted JSON schema could be provided that allows execution of other code by prototype pollution. (While untrusted schemas are recommended against, the worst case of an untrusted schema should be a denial of service, not execution of code.)

Package Name:  minimist  Version :  0.0.8

 Vulnerabilities

CVE ID: CVE-2020-7598
Severity:  medium
Fixed in Version:  0.2.1
Description:  minimist is a parse argument options module. Affected versions of this package are vulnerable to Prototype Pollution. The library could be tricked into adding or modifying properties of Object.prototype using a constructor or __proto__ payload.

 :x: Manifest File: bank-app-backend/pom.xml

Vulnerability Data by Snyk
Package Name:  junit:junit  Version :  4.12

 Vulnerabilities

CVE ID: CVE-2020-15250
Severity:  low
Fixed in Version:  4.13.1
Description:  junit:junit is an unit testing framework for Java Affected versions of this package are vulnerable to Information Exposure. The JUnit4 test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.

Note: This vulnerability does not allow other users to overwrite the contents of these directories or files.
This only affects Unix like systems.

IBM Cloud Continuous Delivery Deployment Configuration Analysis
:white_check_mark:    Manifest File: bank-app-backend/transaction-service/deployment.yaml
:white_check_mark:    Manifest File: bank-app-backend/user-service/deployment.yaml
:white_check_mark:    Manifest File: bank-user-cleanup-utility/job.yaml
:white_check_mark:    Manifest File: pipelines/deployments/transaction.yaml
:white_check_mark:    Manifest File: pipelines/deployments/user.yaml
:white_check_mark:    Manifest File: pipelines/sonarqube.yaml
 Configuration risks discovered in the following manifest file(s)

 :x:    Manifest File: data_model/drop-schema/job.yaml

 Resource Name: cc-schema-unload Namespace: default
Container  Name: cc-schema-unload
Overall Risk: `medium`
Description: Ensure memory usage for container is limited
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If correct memory limits are not set on each container, one process can expand its usage and cause other containers to run out of resources.`
CIS Reference: 5.10

Container  Name: cc-schema-unload
Description: Ensure containers are not in `default` namespace

Container  Name: cc-schema-unload
Overall Risk: `medium`
Description: Ensure CPU priority is set appropriately on the container
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If you do not correctly assign CPU thresholds, the container process may run out of resources and become unresponsive. If CPU resources on the host are not constrainted, CPU shares do not place any restrictions on individual resources.`
CIS Reference: 5.11

 :x:    Manifest File: data_model/job.yaml

 Resource Name: cc-schema-load Namespace: default
Container  Name: cc-schema-load
Description: Ensure containers are not in `default` namespace

Container  Name: cc-schema-load
Overall Risk: `medium`
Description: Ensure memory usage for container is limited
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If correct memory limits are not set on each container, one process can expand its usage and cause other containers to run out of resources.`
CIS Reference: 5.10

Container  Name: cc-schema-load
Overall Risk: `medium`
Description: Ensure CPU priority is set appropriately on the container
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If you do not correctly assign CPU thresholds, the container process may run out of resources and become unresponsive. If CPU resources on the host are not constrainted, CPU shares do not place any restrictions on individual resources.`
CIS Reference: 5.11

 :x:    Manifest File: deployment.yaml

 Resource Name: mobile-simulator-service Namespace: default
Container  Name:
Description: Ensure containers are not exposed through a node port

 Resource Name: mobile-simulator-deployment Namespace: default
Container  Name: mobile-simulator
Description: Ensure containers are not in `default` namespace

Container  Name: mobile-simulator
Overall Risk: `medium`
Description: Ensure memory usage for container is limited
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If correct memory limits are not set on each container, one process can expand its usage and cause other containers to run out of resources.`
CIS Reference: 5.10

Container  Name: mobile-simulator
Overall Risk: `medium`
Description: Ensure CPU priority is set appropriately on the container
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If you do not correctly assign CPU thresholds, the container process may run out of resources and become unresponsive. If CPU resources on the host are not constrainted, CPU shares do not place any restrictions on individual resources.`
CIS Reference: 5.11

 :x:    Manifest File: pipelines/deployments/ui.yaml

 Resource Name: mobile-simulator-service Namespace: default
Container  Name:
Description: Ensure containers are not exposed through a node port

 Resource Name: mobile-simulator-deployment Namespace: default
Container  Name: mobile-simulator
Overall Risk: `medium`
Description: Ensure CPU priority is set appropriately on the container
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If you do not correctly assign CPU thresholds, the container process may run out of resources and become unresponsive. If CPU resources on the host are not constrainted, CPU shares do not place any restrictions on individual resources.`
CIS Reference: 5.11

Container  Name: mobile-simulator
Overall Risk: `medium`
Description: Ensure memory usage for container is limited
Vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`
Impact: `If correct memory limits are not set on each container, one process can expand its usage and cause other containers to run out of resources.`
CIS Reference: 5.10

Container  Name: mobile-simulator
Description: Ensure containers are not in `default` namespace

 :x:    Manifest File: scripts/pg_deploy.yaml

 Resource Name: postgresql-operator Namespace: example-bank
Container  Name: postgresql-operator
Description: Ensure containers are not in `default` namespace

IBM Cloud Continuous Delivery Bill of Materials
 Download Bill of Materials Report: [JSON Format]
Bill of Materials Diff
Compare To: [Branch = main] [Commitid = 704801fed76691352a88b7ccc19dd14c25cd6097]

IBM Cloud Continuous Delivery Vulnerability Report

 :white_check_mark: Manifest File: bank-user-cleanup-utility/Dockerfile-adoptopenjdk:8-jre-openj9

Vulnerability Data by Clair
No OS package vulnerabilities found

 :white_check_mark: Manifest File: bank-app-backend/user-service/Dockerfile-open-liberty:<IP_ADDRESS>-kernel-java8-openj9

Vulnerability Data by Clair
No OS package vulnerabilities found

 :white_check_mark: Manifest File: bank-app-backend/integration-tests/pom.xml

Vulnerability Data by Snyk
No application package vulnerabilities found

 :white_check_mark: Manifest File: bank-app-backend/transaction-service/pom.xml

Vulnerability Data by Snyk
No application package vulnerabilities found

 :white_check_mark: Manifest File: bank-app-backend/user-service/pom.xml

Vulnerability Data by Snyk
No application package vulnerabilities found

 :white_check_mark: Manifest File: bank-app-backend/common/pom.xml

Vulnerability Data by Snyk
No application package vulnerabilities found

 :x: Manifest File: data_model/Dockerfile-postgres:latest

Vulnerability Data by Clair
Package Name:  wget  Version :  1.19.4-1ubuntu2.2

 Vulnerabilities

CVE ID: CVE-2018-20483
Severity:  Negligible
Fixed in Version:  1.20.1-1
Description:  set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

CVE ID: CVE-2018-20483
Severity:  Negligible
Fixed in Version:  1.20.1-1
Description:  set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

CVE ID: CVE-2018-20483
Severity:  Negligible
Fixed in Version:  1.20.1-1
Description:  set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

CVE ID: CVE-2018-0494
Severity:  Medium
Fixed in Version:  1.19.5-1
Description:  GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

CVE ID: CVE-2018-20483
Severity:  Negligible
Fixed in Version:  1.20.1-1
Description:  set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

CVE ID: CVE-2018-20483
Severity:  Negligible
Fixed in Version:  1.20.1-1
Description:  set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.

CVE ID: CVE-2019-5953
Severity:  Unknown
Fixed in Version:  1.20.1-1.1
Description:  Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

CVE ID: CVE-2019-5953
Severity:  High
Fixed in Version:  1.20.1-1.1
Description:  Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

CVE ID: CVE-2018-0494
Severity:  Unknown
Fixed in Version:  1.19.5-1
Description:  GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

CVE ID: CVE-2018-0494
Severity:  Medium
Fixed in Version:  1.19.5-1
Description:  GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

CVE ID: CVE-2019-5953
Severity:  High
Fixed in Version:  1.20.1-1.1
Description:  Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

CVE ID: CVE-2018-0494
Severity:  Medium
Fixed in Version:  1.19.5-1
Description:  GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

CVE ID: CVE-2019-5953
Severity:  High
Fixed in Version:  1.20.1-1.1
Description:  Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

CVE ID: CVE-2019-5953
Severity:  Unknown
Fixed in Version:  1.20.1-1.1
Description:  Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code via unspecified vectors.

CVE ID: CVE-2018-0494
Severity:  Unknown
Fixed in Version:  1.19.5-1
Description:  GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.

Package Name:  unzip  Version :  6.0-21ubuntu1

 Vulnerabilities

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-22
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-22
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2018-1000035
Severity:  Unknown
Fixed in Version:  6.0-22
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2018-1000035
Severity:  Unknown
Fixed in Version:  6.0-22
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-23+deb10u1
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-23+deb10u1
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2018-1000035
Severity:  Medium
Fixed in Version:  6.0-22
Description:  A heap-based buffer overflow exists in Info-Zip UnZip version <= 6.00 in the processing of password-protected archives that allows an attacker to perform a denial of service or to possibly achieve code execution.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-23+deb10u1
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-23+deb10u1
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

CVE ID: CVE-2019-13232
Severity:  Negligible
Fixed in Version:  6.0-23+deb10u1
Description:  Info-ZIP UnZip 6.0 mishandles the overlapping of files inside a ZIP container, leading to denial of service (resource consumption), aka a "better zip bomb" issue.

Package Name:  libgcrypt20  Version :  1.8.1-4ubuntu1.2

 Vulnerabilities

CVE ID: CVE-2018-0495
Severity:  Unknown
Fixed in Version:  1.8.3-1
Description:  Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

CVE ID: CVE-2018-0495
Severity:  Low
Fixed in Version:  1.8.3-1
Description:  Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

CVE ID: CVE-2018-0495
Severity:  Low
Fixed in Version:  1.8.3-1
Description:  Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

CVE ID: CVE-2018-0495
Severity:  Unknown
Fixed in Version:  1.8.3-1
Description:  Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

CVE ID: CVE-2018-0495
Severity:  Low
Fixed in Version:  1.8.3-1
Description:  Libgcrypt before 1.7.10 and 1.8.x before 1.8.3 allows a memory-cache side-channel attack on ECDSA signatures that can be mitigated through the use of blinding during the signing process in the _gcry_ecc_ecdsa_sign function in cipher/ecc-ecdsa.c, aka the Return Of the Hidden Number Problem or ROHNP. To discover an ECDSA key, the attacker needs access to either the local machine or a different virtual machine on the same physical host.

Package Name:  apt  Version :  1.6.12ubuntu0.1

 Vulnerabilities

CVE ID: CVE-2019-3462
Severity:  Critical
Fixed in Version:  1.8.0~alpha3.1
Description:  Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

CVE ID: CVE-2019-3462
Severity:  Critical
Fixed in Version:  1.8.0~alpha3.1
Description:  Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

CVE ID: CVE-2020-3810
Severity:  Medium
Fixed in Version:  <IP_ADDRESS>
Description:  Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

CVE ID: CVE-2020-3810
Severity:  Unknown
Fixed in Version:  <IP_ADDRESS>
Description:  Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

CVE ID: CVE-2020-3810
Severity:  Unknown
Fixed in Version:  <IP_ADDRESS>
Description:  Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

CVE ID: CVE-2019-3462
Severity:  Unknown
Fixed in Version:  1.8.0~alpha3.1
Description:  Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

CVE ID: CVE-2020-3810
Severity:  Medium
Fixed in Version:  <IP_ADDRESS>
Description:  Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

CVE ID: CVE-2019-3462
Severity:  Critical
Fixed in Version:  1.8.0~alpha3.1
Description:  Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

CVE ID: CVE-2019-3462
Severity:  Unknown
Fixed in Version:  1.8.0~alpha3.1
Description:  Incorrect sanitation of the 302 redirect field in HTTP transport method of apt versions 1.4.8 and earlier can lead to content injection by a MITM attacker, potentially leading to remote code execution on the target machine.

CVE ID: CVE-2020-3810
Severity:  Medium
Fixed in Version:  <IP_ADDRESS>
Description:  Missing input validation in the ar/tar implementations of APT before version 2.1.2 could result in denial of service when processing specially crafted deb files.

Package Name:  tar  Version :  1.29b-2ubuntu0.1

 Vulnerabilities

CVE ID: CVE-2018-20482
Severity:  Unknown
Fixed in Version:  1.30+dfsg-3.1
Description:  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 ID: CVE-2018-20482
Severity:  Low
Fixed in Version:  1.30+dfsg-3.1
Description:  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 ID: CVE-2018-20482
Severity:  Unknown
Fixed in Version:  1.30+dfsg-3.1
Description:  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 ID: CVE-2018-20482
Severity:  Low
Fixed in Version:  1.30+dfsg-3.1
Description:  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 ID: CVE-2018-20482
Severity:  Low
Fixed in Version:  1.30+dfsg-3.1
Description:  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).

Package Name:  bzip2  Version :  1.0.6-8.1ubuntu0.2

 Vulnerabilities

CVE ID: CVE-2019-12900
Severity:  High
Fixed in Version:  1.0.6-9.1
Description:  BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

CVE ID: CVE-2019-12900
Severity:  High
Fixed in Version:  1.0.6-9.1
Description:  BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

CVE ID: CVE-2019-12900
Severity:  Unknown
Fixed in Version:  1.0.6-9.1
Description:  BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

CVE ID: CVE-2019-12900
Severity:  Unknown
Fixed in Version:  1.0.6-9.1
Description:  BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

CVE ID: CVE-2019-12900
Severity:  High
Fixed in Version:  1.0.6-9.1
Description:  BZ2_decompress in decompress.c in bzip2 through 1.0.6 has an out-of-bounds write when there are many selectors.

Package Name:  e2fsprogs  Version :  1.44.1-1ubuntu1.3

 Vulnerabilities

CVE ID: CVE-2019-5188
Severity:  Medium
Fixed in Version:  1.44.5-1+deb10u3
Description:  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.

CVE ID: CVE-2019-5188
Severity:  Medium
Fixed in Version:  1.44.5-1+deb10u3
Description:  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.

CVE ID: CVE-2019-5094
Severity:  Medium
Fixed in Version:  1.44.5-1+deb10u2
Description:  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 ID: CVE-2019-5188
Severity:  Unknown
Fixed in Version:  1.44.5-1+deb10u3
Description:  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.

CVE ID: CVE-2019-5094
Severity:  Medium
Fixed in Version:  1.44.5-1+deb10u2
Description:  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 ID: CVE-2019-5094
Severity:  Unknown
Fixed in Version:  1.44.5-1+deb10u2
Description:  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 ID: CVE-2019-5094
Severity:  Medium
Fixed in Version:  1.44.5-1+deb10u2
Description:  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 ID: CVE-2019-5188
Severity:  Unknown
Fixed in Version:  1.44.5-1+deb10u3
Description:  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.

CVE ID: CVE-2019-5094
Severity:  Unknown
Fixed in Version:  1.44.5-1+deb10u2
Description:  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 ID: CVE-2019-5188
Severity:  Medium
Fixed in Version:  1.44.5-1+deb10u3
Description:  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.

Package Name:  util-linux  Version :  2.31.1-0.4ubuntu3.7

 Vulnerabilities

CVE ID: CVE-2018-7738
Severity:  Negligible
Fixed in Version:  2.31.1-0.5
Description:  In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

CVE ID: CVE-2018-7738
Severity:  Negligible
Fixed in Version:  2.31.1-0.5
Description:  In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

CVE ID: CVE-2018-7738
Severity:  Negligible
Fixed in Version:  2.31.1-0.5
Description:  In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

CVE ID: CVE-2018-7738
Severity:  Negligible
Fixed in Version:  2.31.1-0.5
Description:  In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

CVE ID: CVE-2018-7738
Severity:  Negligible
Fixed in Version:  2.31.1-0.5
Description:  In util-linux before 2.32-rc1, bash-completion/umount allows local users to gain privileges by embedding shell commands in a mountpoint name, which is mishandled during a umount command (within Bash) by a different user, as demonstrated by logging in as root and entering umount followed by a tab character for autocompletion.

Package Name:  openssl  Version :  1.1.1-1ubuntu2.1~18.04.6

 Vulnerabilities

CVE ID: CVE-2019-1563
Severity:  Medium
Fixed in Version:  1.1.1d-0+deb10u1
Description:  In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2020-1967
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u3
Description:  Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1
Description:  OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

CVE ID: CVE-2019-1547
Severity:  Low
Fixed in Version:  1.1.1d-0+deb10u1
Description:  Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2019-1547
Severity:  Unknown
Fixed in Version:  1.1.1d-0+deb10u1
Description:  Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2019-1543
Severity:  Low
Fixed in Version:  1.1.1c-1
Description:  ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

CVE ID: CVE-2018-0734
Severity:  Medium
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

CVE ID: CVE-2018-0735
Severity:  Negligible
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

CVE ID: CVE-2019-1547
Severity:  Unknown
Fixed in Version:  1.1.1d-0+deb10u1
Description:  Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1
Description:  OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

CVE ID: CVE-2018-0734
Severity:  Unknown
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL DSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.1a (Affected 1.1.1). Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.0.2q (Affected 1.0.2-1.0.2p).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1
Description:  OpenSSL 1.1.1 introduced a rewritten random number generator (RNG). This was intended to include protection in the event of a fork() system call in order to ensure that the parent and child processes did not share the same RNG state. However this protection was not being used in the default case. A partial mitigation for this issue is that the output from a high precision timer is mixed into the RNG state so the likelihood of a parent and child process sharing state is significantly reduced. If an application already calls OPENSSL_init_crypto() explicitly using OPENSSL_INIT_ATFORK then this problem does not occur at all. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c).

CVE ID: CVE-2019-1563
Severity:  Medium
Fixed in Version:  1.1.1d-0+deb10u1
Description:  In situations where an attacker receives automated notification of the success or failure of a decryption attempt an attacker, after sending a very large number of messages to be decrypted, can recover a CMS/PKCS7 transported encryption key or decrypt any RSA encrypted message that was encrypted with the public RSA key, using a Bleichenbacher padding oracle attack. Applications are not affected if they use a certificate together with the private RSA key to the CMS_decrypt or PKCS7_decrypt functions to select the correct recipient info to decrypt. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s).

CVE ID: CVE-2020-1967
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u3
Description:  Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due to a NULL pointer dereference as a result of incorrect handling of the "signature_algorithms_cert" TLS extension. The crash occurs if an invalid or unrecognised signature algorithm is received from the peer. This could be exploited by a malicious peer in a Denial of Service attack. OpenSSL version 1.1.1d, 1.1.1e, and 1.1.1f are affected by this issue. This issue did not affect OpenSSL versions prior to 1.1.1d. Fixed in OpenSSL 1.1.1g (Affected 1.1.1d-1.1.1f).

CVE ID: CVE-2018-0735
Severity:  Negligible
Fixed in Version:  1.1.1a-1
Description:  The OpenSSL ECDSA signature algorithm has been shown to be vulnerable to a timing side channel attack. An attacker could use variations in the signing algorithm to recover the private key. Fixed in OpenSSL 1.1.0j (Affected 1.1.0-1.1.0i). Fixed in OpenSSL 1.1.1a (Affected 1.1.1).

CVE ID: CVE-2019-1549
Severity:  Negligible
Fixed in Version:  1.1.1d-0+deb10u1