# Snyk test report

October 29th 2023, 12:22:23 am (UTC+00:00)

Scanned the following path:

- redis:7.0.11-alpine (apk)

5 known vulnerabilities
41 vulnerable dependency paths
18 dependencies

Project | docker-image|redis
Path | redis:7.0.11-alpine
Package Manager | apk

## Out-of-bounds Write

critical severity

- Package Manager: alpine:3.18
- Vulnerable module: busybox/busybox
- Introduced through: docker-image|redis@7.0.11-alpine and busybox/busybox@1.36.1-r0

### Detailed paths

- Introduced through: docker-image|redis@7.0.11-alpine › busybox/busybox@1.36.1-r0
- Introduced through: docker-image|redis@7.0.11-alpine › alpine-baselayout/alpine-baselayout@3.4.3-r1 › busybox/busybox-binsh@1.36.1-r0 › busybox/busybox@1.36.1-r0
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/busybox-binsh@1.36.1-r0
- Introduced through: docker-image|redis@7.0.11-alpine › alpine-baselayout/alpine-baselayout@3.4.3-r1 › busybox/busybox-binsh@1.36.1-r0
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `busybox` package and not the `busybox` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.18` relevant fixed versions and status.

There is a stack overflow vulnerability in ash.c:6030 in busybox before 1.35. In the environment of Internet of Vehicles, this vulnerability can be executed from command to arbitrary code execution.

## Remediation

Upgrade `Alpine:3.18` `busybox` to version 1.36.1-r1 or higher.

## References

- cve@mitre.org

More about this vulnerability

## Improper Authentication

medium severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|redis@7.0.11-alpine and openssl/libcrypto3@3.1.1-r1

### Detailed paths

- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libssl3@3.1.1-r1

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine:3.18`. See `How to fix?` for `Alpine:3.18` relevant fixed versions and status.

Issue summary: The AES-SIV cipher implementation contains a bug that causes it to ignore empty associated data entries which are unauthenticated as a consequence.

Impact summary: Applications that use the AES-SIV algorithm and want to authenticate empty data entries as associated data can be mislead by removing adding or reordering such empty entries as these are ignored by the OpenSSL implementation. We are currently unaware of any such applications.

The AES-SIV algorithm allows for authentication of multiple associated data entries along with the encryption. To authenticate empty data the application has to call EVP_EncryptUpdate() (or EVP_CipherUpdate()) with NULL pointer as the output buffer and 0 as the input buffer length. The AES-SIV implementation in OpenSSL just returns success for such a call instead of performing the associated data authentication operation. The empty data thus will not be authenticated.

As this issue does not affect non-empty associated data authentication and we expect it to be rare for an application to use empty associated data entries this is qualified as Low severity issue.

## Remediation

Upgrade `Alpine:3.18` `openssl` to version 3.1.1-r2 or higher.

## References

- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org

More about this vulnerability

## Inefficient Regular Expression Complexity

medium severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|redis@7.0.11-alpine and openssl/libcrypto3@3.1.1-r1

### Detailed paths

- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libssl3@3.1.1-r1

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.18` relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.

However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.

The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

## Remediation

Upgrade `Alpine:3.18` `openssl` to version 3.1.1-r3 or higher.

## References

- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org

More about this vulnerability

## Excessive Iteration

medium severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|redis@7.0.11-alpine and openssl/libcrypto3@3.1.1-r1

### Detailed paths

- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libssl3@3.1.1-r1

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.18` relevant fixed versions and status.

Issue summary: Checking excessively long DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.

The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.

An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.

The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().

Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.

## Remediation

Upgrade `Alpine:3.18` `openssl` to version 3.1.2-r0 or higher.

## References

- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org

More about this vulnerability

## CVE-2023-5363

low severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|redis@7.0.11-alpine and openssl/libcrypto3@3.1.1-r1

### Detailed paths

- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1 › openssl/libcrypto3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › .redis-rundeps@20230614.215749 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.1-r1
- Introduced through: docker-image|redis@7.0.11-alpine › busybox/ssl_client@1.36.1-r0 › openssl/libssl3@3.1.1-r1

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.18` relevant fixed versions and status.

Issue summary: A bug has been identified in the processing of key and initialisation vector (IV) lengths. This can lead to potential truncation or overruns during the initialisation of some symmetric ciphers.

Impact summary: A truncation in the IV can result in non-uniqueness, which could result in loss of confidentiality for some cipher modes.

When calling EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() or EVP_CipherInit_ex2() the provided OSSL_PARAM array is processed after the key and IV have been established. Any alterations to the key length, via the "keylen" parameter or the IV length, via the "ivlen" parameter, within the OSSL_PARAM array will not take effect as intended, potentially causing truncation or overreading of these values. The following ciphers and cipher modes are impacted: RC2, RC4, RC5, CCM, GCM and OCB.

For the CCM, GCM and OCB cipher modes, truncation of the IV can result in loss of confidentiality. For example, when following NIST's SP 800-38D section 8.2.1 guidance for constructing a deterministic IV for AES in GCM mode, truncation of the counter portion could lead to IV reuse.

Both truncations and overruns of the key and overruns of the IV will produce incorrect results and could, in some cases, trigger a memory exception. However, these issues are not currently assessed as security critical.

Changing the key and/or IV lengths is not considered to be a common operation and the vulnerable API was recently introduced. Furthermore it is likely that application developers will have spotted this problem during testing since decryption would fail unless both peers in the communication were similarly vulnerable. For these reasons we expect the probability of an application being vulnerable to this to be quite low. However if an application is vulnerable then this issue is considered very serious. For these reasons we have assessed this issue as Moderate severity overall.

The OpenSSL SSL/TLS implementation is not affected by this issue.

The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this because the issue lies outside of the FIPS provider boundary.

OpenSSL 3.1 and 3.0 are vulnerable to this issue.

## Remediation

Upgrade `Alpine:3.18` `openssl` to version 3.1.4-r0 or higher.

## References

- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org
- openssl-security@openssl.org

More about this vulnerability