Security vulnerabilities in "redis:7.0.14-alpine"

[donegjookim]

Details and Impact [openssl 3.1.4-r2][https://github.com/advisories/GHSA-wm78-9prw-c5h4]: 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.

[redis-server 7.0.14][https://github.com/advisories/GHSA-9v9h-cgj8-h64p]: Redis is an in-memory database that persists on disk. Redis incorrectly handles resizing of memory buffers which can result in integer overflow that leads to heap overflow and potential remote code execution. This issue has been patched in version 7.0.15 and 7.2.4.

[busybox 1.36.1-r15][CVE-2023-41056]: A use-after-free vulnerability was discovered in xasprintf function in xfuncs_printf.c:344 in BusyBox v.1.36.1.

[busybox 1.36.1-r15][CVE-2023-6992]: A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159.

[zlib 1.3-r2][https://github.com/advisories/GHSA-2vjj-r39q-gvxr]: A heap-buffer-overflow was discovered in BusyBox v.1.36.1 in the next_token function at awk.c:1159.

[todaywasawesome]

@donegjookim you can always manually select your Redis images as a workaround while waiting for the update.

[todaywasawesome]

Looking at the Redis images they all have some open CVEs it looks like. https://hub.docker.com/_/redis/tags

[christianh814]

Looking at the Redis images they all have some open CVEs it looks like. https://hub.docker.com/_/redis/tags

Seems like there's not much we can do other than "wait" :(