Docker docker:test
Vulnerabilities |
3 via 6 paths |
|---|---|
Dependencies |
20 |
Source |
Docker |
Target OS |
alpine:3.12.1 |
medium severity
- Vulnerable module: musl/musl
- Introduced through: musl/musl@1.1.24-r9 and musl/musl-utils@1.1.24-r9
- Fixed in: 1.1.24-r10
Detailed paths
-
Introduced through: docker:test@* › musl/musl@1.1.24-r9
-
Introduced through: docker:test@* › musl/musl-utils@1.1.24-r9
Overview
Affected versions of this package are vulnerable to Out-of-bounds Write. In musl libc through 1.2.1, wcsnrtombs mishandles particular combinations of destination buffer size and source character limit, as demonstrated by an invalid write access (buffer overflow).
Remediation
Upgrade musl to version or higher.
References
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@8.3_p1-r0 and openssh/openssh-keygen@8.3_p1-r0
- Fixed in: 8.3_p1-r1
Detailed paths
-
Introduced through: docker:test@* › openssh/openssh-client@8.3_p1-r0
-
Introduced through: docker:test@* › openssh/openssh-keygen@8.3_p1-r0
Overview
Affected versions of this package are vulnerable to Information Exposure. The client side in OpenSSH 5.7 through 8.3 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client).
Remediation
Upgrade openssh to version or higher.
References
medium severity
- Vulnerable module: openssl/libcrypto1.1
- Introduced through: openssl/libcrypto1.1@1.1.1g-r0 and openssl/libssl1.1@1.1.1g-r0
- Fixed in: 1.1.1i-r0
Detailed paths
-
Introduced through: docker:test@* › openssl/libcrypto1.1@1.1.1g-r0
-
Introduced through: docker:test@* › openssl/libssl1.1@1.1.1g-r0
Overview
Affected versions of this package are vulnerable to NULL Pointer Dereference. The X.509 GeneralName type is a generic type for representing different types of names. One of those name types is known as EDIPartyName. OpenSSL provides a function GENERAL_NAME_cmp which compares different instances of a GENERAL_NAME to see if they are equal or not. This function behaves incorrectly when both GENERAL_NAMEs contain an EDIPARTYNAME. A NULL pointer dereference and a crash may occur leading to a possible denial of service attack. OpenSSL itself uses the GENERAL_NAME_cmp function for two purposes: 1) Comparing CRL distribution point names between an available CRL and a CRL distribution point embedded in an X509 certificate 2) When verifying that a timestamp response token signer matches the timestamp authority name (exposed via the API functions TS_RESP_verify_response and TS_RESP_verify_token) If an attacker can control both items being compared then that attacker could trigger a crash. For example if the attacker can trick a client or server into checking a malicious certificate against a malicious CRL then this may occur. Note that some applications automatically download CRLs based on a URL embedded in a certificate. This checking happens prior to the signatures on the certificate and CRL being verified. OpenSSL's s_server, s_client and verify tools have support for the "-crl_download" option which implements automatic CRL downloading and this attack has been demonstrated to work against those tools. Note that an unrelated bug means that affected versions of OpenSSL cannot parse or construct correct encodings of EDIPARTYNAME. However it is possible to construct a malformed EDIPARTYNAME that OpenSSL's parser will accept and hence trigger this attack. All OpenSSL 1.1.1 and 1.0.2 versions are affected by this issue. Other OpenSSL releases are out of support and have not been checked. Fixed in OpenSSL 1.1.1i (Affected 1.1.1-1.1.1h). Fixed in OpenSSL 1.0.2x (Affected 1.0.2-1.0.2w).
Remediation
Upgrade openssl to version or higher.