# Snyk test report

March 24th 2024, 12:20:01 am (UTC+00:00)

Scanned the following path:

- haproxy:2.6.14-alpine (apk)

5 known vulnerabilities
45 vulnerable dependency paths
18 dependencies

Project | docker-image|haproxy
Path | haproxy:2.6.14-alpine
Package Manager | apk

## CVE-2023-5363

high severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|haproxy@2.6.14-alpine and openssl/libcrypto3@3.1.2-r0

### Detailed paths

- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libssl3@3.1.2-r0

## 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
- openssl-security@openssl.org
- openssl-security@openssl.org

More about this vulnerability

## Improper Check for Unusual or Exceptional Conditions

medium severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|haproxy@2.6.14-alpine and openssl/libcrypto3@3.1.2-r0

### Detailed paths

- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libssl3@3.1.2-r0

## 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: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.

Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 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.

While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.

Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.

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

DH_generate_key() and DH_check_pub_key() are also 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_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().

Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.

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.4-r1 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

More about this vulnerability

## Out-of-bounds Write

medium severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|haproxy@2.6.14-alpine and openssl/libcrypto3@3.1.2-r0

### Detailed paths

- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libssl3@3.1.2-r0

## 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: The POLY1305 MAC (message authentication code) implementation contains a bug that might corrupt the internal state of applications running on PowerPC CPU based platforms if the CPU provides vector instructions.

Impact summary: If an attacker can influence whether the POLY1305 MAC algorithm is used, the application state might be corrupted with various application dependent consequences.

The POLY1305 MAC (message authentication code) implementation in OpenSSL for PowerPC CPUs restores the contents of vector registers in a different order than they are saved. Thus the contents of some of these vector registers are corrupted when returning to the caller. The vulnerable code is used only on newer PowerPC processors supporting the PowerISA 2.07 instructions.

The consequences of this kind of internal application state corruption can be various - from no consequences, if the calling application does not depend on the contents of non-volatile XMM registers at all, to the worst consequences, where the attacker could get complete control of the application process. However unless the compiler uses the vector registers for storing pointers, the most likely consequence, if any, would be an incorrect result of some application dependent calculations or a crash leading to a denial of service.

The POLY1305 MAC algorithm is most frequently used as part of the CHACHA20-POLY1305 AEAD (authenticated encryption with associated data) algorithm. The most common usage of this AEAD cipher is with TLS protocol versions 1.2 and 1.3. If this cipher is enabled on the server a malicious client can influence whether this AEAD cipher is used. This implies that TLS server applications using OpenSSL can be potentially impacted. However we are currently not aware of any concrete application that would be affected by this issue therefore we consider this a Low severity security issue.

## Remediation

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

## References

- https://github.com/openssl/openssl/commit/050d26383d4e264966fb83428e72d5d48f402d35
- https://github.com/openssl/openssl/commit/5b139f95c9a47a55a0c54100f3837b1eee942b04
- https://github.com/openssl/openssl/commit/f3fc5808fe9ff74042d639839610d03b8fdcc015
- https://www.openssl.org/news/secadv/20240109.txt
- http://www.openwall.com/lists/oss-security/2024/01/09/1
- https://security.netapp.com/advisory/ntap-20240216-0009/

More about this vulnerability

## CVE-2024-0727

medium severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|haproxy@2.6.14-alpine and openssl/libcrypto3@3.1.2-r0

### Detailed paths

- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libssl3@3.1.2-r0

## 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: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack

Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.

A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.

OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().

We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.

The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.

## Remediation

Upgrade `Alpine:3.18` `openssl` to version 3.1.4-r5 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

More about this vulnerability

## CVE-2023-6237

low severity

- Package Manager: alpine:3.18
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|haproxy@2.6.14-alpine and openssl/libcrypto3@3.1.2-r0

### Detailed paths

- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0 › openssl/libcrypto3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › .haproxy-rundeps@20230809.001942 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › apk-tools/apk-tools@2.14.0-r2 › openssl/libssl3@3.1.2-r0
- Introduced through: docker-image|haproxy@2.6.14-alpine › busybox/ssl_client@1.36.1-r2 › openssl/libssl3@3.1.2-r0

## NVD Description

This vulnerability has not been analyzed by NVD yet.

## Remediation

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

More about this vulnerability