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 (CVE-2022-24963) or cause a denial of service (CVE-2023-44487) by sending specially crafted network requests. Disabling HTTP/2 (mod_http2) would fully eliminate CVE-2023-44487, but the remaining critical vulnerabilities still require patching.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-24963 | CRITICAL9.8 | apr 1.7.0-r1 fixed in 1.7.1-r0 | 1.5% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-44487 | CRITICAL9.75 | nghttp2-libs 1.47.0-r0 fixed in 1.47.0-r2 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2022-37434 | HIGH8 | zlib 1.2.12-r1 fixed in 1.2.12-r2 | 16.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0286 | HIGH7.7 | libssl1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 59.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-52425 | HIGH7.5 | expat 2.4.8-r0 fixed in 2.6.0-r0 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | expat 2.4.8-r0 fixed in 2.6.2-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35940 | HIGH7.1 | apr 1.7.0-r1 fixed in 1.7.0-r2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40303 | MEDIUM6.9 | libxml2 2.9.14-r0 fixed in 2.9.14-r2 | 22.8% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-4304 | MEDIUM6.79 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | apr 1.7.0-r1 fixed in 1.7.1-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | apr-util 1.6.1-r12 fixed in 1.6.3-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | apr-util-ldap 1.6.1-r12 fixed in 1.6.3-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40674 | MEDIUM6.48 | expat 2.4.8-r0 fixed in 2.4.9-r0 | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-43680 | MEDIUM6 | expat 2.4.8-r0 fixed in 2.5.0-r0 | 2.2% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0464 | MEDIUM6 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-0464 | MEDIUM6 | libssl1.1 1.1.1o-r0 fixed in 1.1.1t-r1 | 3.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-35945 | MEDIUM6 | nghttp2-libs 1.47.0-r0 fixed in 1.47.0-r1 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.3-r0 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1u-r2 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1o-r0 fixed in 1.1.1q-r0 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1o-r0 fixed in 1.1.1t-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1o-r0 fixed in 1.1.1u-r2 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1o-r0 fixed in 1.1.1v-r0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1o-r0 fixed in 1.1.1w-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1u-r0 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2023-2650 | MEDIUM5.07 | libssl1.1 1.1.1o-r0 fixed in 1.1.1u-r0 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | expat 2.4.8-r0 fixed in 2.6.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-23914 | MEDIUM4.64 | libcurl 7.83.1-r1 fixed in 7.83.1-r6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | libcurl 7.83.1-r1 fixed in 8.4.0-r0 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2022-42916 | MEDIUM4.5 | libcurl 7.83.1-r1 fixed in 7.83.1-r4 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28319 | MEDIUM4.5 | libcurl 7.83.1-r1 fixed in 8.1.0-r0 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32206 | MEDIUM4.48 | libcurl 7.83.1-r1 fixed in 7.83.1-r2 | 32.0% High Exploitation Risk | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl 5.34.1-r0 fixed in 5.34.2-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl 7.83.1-r1 fixed in 7.83.1-r6 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl 7.83.1-r1 fixed in 8.5.0-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-26519 | LOW3.57 | musl-utils 1.2.3-r0 fixed in 1.2.3-r4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl 7.83.1-r1 fixed in 7.83.1-r2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl 7.83.1-r1 fixed in 7.83.1-r5 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl 7.83.1-r1 fixed in 8.0.1-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl 7.83.1-r1 fixed in 8.0.1-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27537 | LOW3.54 | libcurl 7.83.1-r1 fixed in 8.0.1-r0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28320 | LOW3.54 | libcurl 7.83.1-r1 fixed in 8.1.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl 7.83.1-r1 fixed in 8.1.0-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-28331 | LOW3.53 | apr 1.7.0-r1 fixed in 1.7.1-r0 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32207 | LOW3.53 | libcurl 7.83.1-r1 fixed in 7.83.1-r2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32221 | LOW3.53 | libcurl 7.83.1-r1 fixed in 7.83.1-r4 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38039 | LOW3.51 | libcurl 7.83.1-r1 fixed in 8.3.0-r0 | 62.2% Actively Exploited | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | libcurl 7.83.1-r1 fixed in 7.83.1-r6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl 7.83.1-r1 fixed in 8.0.1-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl 7.83.1-r1 fixed in 8.5.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl 7.83.1-r1 fixed in 8.0.1-r0 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl 7.83.1-r1 fixed in 8.0.1-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2022-43551 | LOW3.1 | libcurl 7.83.1-r1 fixed in 7.83.1-r5 | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libssl1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2022-32205 | LOW2.97 | libcurl 7.83.1-r1 fixed in 7.83.1-r2 | 26.9% High Exploitation Risk | Post-Exploit |
| CVE-2022-42915 | LOW2.92 | libcurl 7.83.1-r1 fixed in 7.83.1-r4 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-30065 | LOW2.81 | busybox 1.35.0-r13 fixed in 1.35.0-r15 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-40304 | LOW2.81 | libxml2 2.9.14-r0 fixed in 2.9.14-r2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-30065 | LOW2.81 | ssl_client 1.35.0-r13 fixed in 1.35.0-r15 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.35.0-r13 fixed in 1.35.0-r18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.35.0-r13 fixed in 1.35.0-r18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libcrypto1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libssl1.1 1.1.1o-r0 fixed in 1.1.1t-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-2309 | LOW2.7 | libxml2 2.9.14-r0 fixed in 2.9.14-r1 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl 7.83.1-r1 fixed in 7.83.1-r3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl 7.83.1-r1 fixed in 8.1.0-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl 7.83.1-r1 fixed in 8.4.0-r0 | 6.2% Low-Moderate Risk | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.