Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve remote code execution by sending crafted requests exploiting buffer overflows in APR (CVE-2022-24963) or zlib (CVE-2018-25032), leading to full server compromise. These vulnerabilities are in core libraries (APR, zlib) used by every request and require no special configuration to exploit. While some other vulnerabilities require optional modules (e.g., expat for XML parsing), the critical flaws are always active. No effective compensating controls exist short of rebuilding the image with patched packages.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-24963 | CRITICAL9.8 | apr 1.7.0-r0 fixed in 1.7.1-r0 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2018-25032 | CRITICAL9.75 | zlib 1.2.11-r3 fixed in 1.2.12-r0 | 52.1% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2022-22827 | HIGH8.8 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl 2.1.27-r12 fixed in 2.1.28-r0 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libssl1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-40303 | HIGH8.62 | libxml2 2.9.12-r1 fixed in 2.9.14-r2 | 22.8% High Exploitation Risk | Directly Exposed |
| CVE-2022-40674 | HIGH8.1 | expat 2.4.1-r0 fixed in 2.4.9-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25236 | HIGH8 | expat 2.4.1-r0 fixed in 2.4.5-r0 | 34.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-37434 | HIGH8 | zlib 1.2.11-r3 fixed in 1.2.12-r2 | 16.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22822 | HIGH7.84 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 4.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22823 | HIGH7.84 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 3.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22824 | HIGH7.84 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 3.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23852 | HIGH7.84 | expat 2.4.1-r0 fixed in 2.4.4-r0 | 4.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-25235 | HIGH7.84 | expat 2.4.1-r0 fixed in 2.4.5-r0 | 5.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-25315 | HIGH7.84 | expat 2.4.1-r0 fixed in 2.4.5-r0 | 4.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-46143 | HIGH7.8 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40304 | HIGH7.8 | libxml2 2.9.12-r1 fixed in 2.9.14-r2 | 6.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0778 | HIGH7.8 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1n-r0 | 70.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2022-0778 | HIGH7.8 | libretls 3.3.3p1-r2 fixed in 3.3.3p1-r3 | 70.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2022-0778 | HIGH7.8 | libssl1.1 1.1.1l-r0 fixed in 1.1.1n-r0 | 70.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | libssl1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23990 | HIGH7.5 | expat 2.4.1-r0 fixed in 2.4.4-r0 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25314 | HIGH7.5 | expat 2.4.1-r0 fixed in 2.4.5-r0 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43680 | HIGH7.5 | expat 2.4.1-r0 fixed in 2.5.0-r0 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | libssl1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libssl1.1 1.1.1l-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2309 | HIGH7.5 | libxml2 2.9.12-r1 fixed in 2.9.14-r1 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23308 | HIGH7.5 | libxml2 2.9.12-r1 fixed in 2.9.13-r0 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35940 | HIGH7.1 | apr 1.7.0-r0 fixed in 1.7.0-r1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45960 | HIGH7.04 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 4.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22825 | HIGH7.04 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22826 | HIGH7.04 | expat 2.4.1-r0 fixed in 2.4.3-r0 | 2.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-4304 | MEDIUM6.79 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1l-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | apr 1.7.0-r0 fixed in 1.7.1-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | apr-util 1.6.1-r7 fixed in 1.6.3-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | apr-util-ldap 1.6.1-r7 fixed in 1.6.3-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25313 | MEDIUM6.5 | expat 2.4.1-r0 fixed in 2.4.5-r0 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29824 | MEDIUM6.5 | libxml2 2.9.12-r1 fixed in 2.9.14-r0 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libcrypto1.1 1.1.1l-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1l-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1l-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libuuid 2.37-r0 fixed in 2.37.2-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3995 | MEDIUM4.67 | libuuid 2.37-r0 fixed in 2.37.3-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-3996 | MEDIUM4.67 | libuuid 2.37-r0 fixed in 2.37.3-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid 2.37-r0 fixed in 2.37.4-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27782 | MEDIUM4.5 | libcurl 7.79.0-r0 fixed in 7.79.1-r2 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32206 | MEDIUM4.48 | libcurl 7.79.0-r0 fixed in 7.79.1-r2 | 32.0% High Exploitation Risk | Post-Exploit |
| CVE-2021-42378 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42379 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42380 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42381 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42385 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42386 | MEDIUM4.32 | busybox 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42378 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42379 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42380 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42381 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42382 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42383 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42384 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42385 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42386 | MEDIUM4.32 | ssl_client 1.33.1-r3 fixed in 1.33.1-r6 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | libcurl 7.79.0-r0 fixed in 7.79.1-r1 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl 7.79.0-r0 fixed in 7.79.1-r5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl 7.79.0-r0 fixed in 7.79.1-r2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl 7.79.0-r0 fixed in 7.79.1-r4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl 7.79.0-r0 fixed in 8.0.1-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl 7.79.0-r0 fixed in 8.0.1-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27537 | LOW3.54 | libcurl 7.79.0-r0 fixed in 8.0.1-r0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-28331 | LOW3.53 | apr 1.7.0-r0 fixed in 1.7.1-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32207 | LOW3.53 | libcurl 7.79.0-r0 fixed in 7.79.1-r2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | libcurl 7.79.0-r0 fixed in 7.79.1-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | libcurl 7.79.0-r0 fixed in 7.79.1-r5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl 7.79.0-r0 fixed in 8.0.1-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-28391 | LOW3.17 | busybox 1.33.1-r3 fixed in 1.33.1-r7 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl 7.79.0-r0 fixed in 8.0.1-r0 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl 7.79.0-r0 fixed in 8.0.1-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-28391 | LOW3.17 | ssl_client 1.33.1-r3 fixed in 1.33.1-r7 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | LOW3.17 | xz-libs 5.2.5-r0 fixed in 5.2.5-r1 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43551 | LOW3.1 | libcurl 7.79.0-r0 fixed in 7.79.1-r4 | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2022-32205 | LOW2.97 | libcurl 7.79.0-r0 fixed in 7.79.1-r2 | 26.9% High Exploitation Risk | Post-Exploit |
| CVE-2022-22576 | LOW2.92 | libcurl 7.79.0-r0 fixed in 7.79.1-r1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42375 | LOW2.8 | busybox 1.33.1-r3 fixed in 1.33.1-r5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-42375 | LOW2.8 | ssl_client 1.33.1-r3 fixed in 1.33.1-r5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-23914 | LOW2.78 | libcurl 7.79.0-r0 fixed in 7.79.1-r5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27775 | LOW2.7 | libcurl 7.79.0-r0 fixed in 7.79.1-r1 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | LOW2.7 | libcurl 7.79.0-r0 fixed in 7.79.1-r2 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-42374 | LOW2.7 | busybox 1.33.1-r3 fixed in 1.33.1-r4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-42374 | LOW2.7 | ssl_client 1.33.1-r3 fixed in 1.33.1-r4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl 7.79.0-r0 fixed in 7.79.1-r3 | 1.8% Low-Moderate Risk | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.