Snyk - Open Source Security

Snyk test report

October 5th 2025, 12:22:22 am (UTC+00:00)

Scanned the following path:
  • public.ecr.aws/docker/library/redis:8.2.1-alpine/docker/library/redis (apk)
3 known vulnerabilities
30 vulnerable dependency paths
22 dependencies
Project docker-image|public.ecr.aws/docker/library/redis
Path public.ecr.aws/docker/library/redis:8.2.1-alpine/docker/library/redis
Package Manager apk

CVE-2025-9232

low severity
  • Package Manager: alpine:3.22
  • Vulnerable module: openssl/libcrypto3
  • Introduced through: docker-image|public.ecr.aws/docker/library/[email protected] and openssl/[email protected]

Detailed paths

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.22 relevant fixed versions and status.

Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address.

Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application.

The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker.

In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity.

The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Alpine:3.22 openssl to version 3.5.4-r0 or higher.

References

More about this vulnerability

CVE-2025-9230

low severity
  • Package Manager: alpine:3.22
  • Vulnerable module: openssl/libcrypto3
  • Introduced through: docker-image|public.ecr.aws/docker/library/[email protected] and openssl/[email protected]

Detailed paths

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.22 relevant fixed versions and status.

Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.

Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.

Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Alpine:3.22 openssl to version 3.5.4-r0 or higher.

References

More about this vulnerability

CVE-2025-9231

low severity
  • Package Manager: alpine:3.22
  • Vulnerable module: openssl/libcrypto3
  • Introduced through: docker-image|public.ecr.aws/docker/library/[email protected] and openssl/[email protected]

Detailed paths

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.22 relevant fixed versions and status.

Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms.

Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker..

While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack.

OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.

Remediation

Upgrade Alpine:3.22 openssl to version 3.5.4-r0 or higher.

References

More about this vulnerability