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 via heap buffer overflow in glibc's iconv function (CVE-2024-2961), which is actively used by httpd for character set conversions. Additionally, stack-based buffer overflows in glibc's sunrpc (CVE-2022-23219) and multiple vulnerabilities in expat (CVE-2022-23852) provide further avenues for code execution. Despite its official status, the 154 high-severity or critical vulnerabilities make deployment unacceptable without immediate remediation.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2024-2961 | CRITICAL10 | libc-bin 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-2961 | CRITICAL10 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-2961 | CRITICAL10 | libc6 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2022-23219 | CRITICAL9.8 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23218 | CRITICAL9.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23219 | CRITICAL9.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23852 | CRITICAL9.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25235 | CRITICAL9.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25315 | CRITICAL9.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-18224 | CRITICAL9.8 | libidn2-0 2.0.5-1 fixed in 2.0.5-1+deb10u1 | 3.7% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g 1:1.2.11.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36221 | CRITICAL9.75 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 84.2% Actively Exploited | Directly Exposed |
| CVE-2020-36222 | CRITICAL9.75 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 77.7% Actively Exploited | Directly Exposed |
| CVE-2020-36227 | CRITICAL9.75 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 77.7% Actively Exploited | Directly Exposed |
| CVE-2020-36228 | CRITICAL9.75 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 83.4% Actively Exploited | Directly Exposed |
| CVE-2021-27212 | CRITICAL9.75 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u6 | 64.1% Actively Exploited | Directly Exposed |
| CVE-2020-36221 | CRITICAL9.75 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 84.2% Actively Exploited | Directly Exposed |
| CVE-2020-36222 | CRITICAL9.75 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 77.7% Actively Exploited | Directly Exposed |
| CVE-2020-36227 | CRITICAL9.75 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 77.7% Actively Exploited | Directly Exposed |
| CVE-2020-36228 | CRITICAL9.75 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 83.4% Actively Exploited | Directly Exposed |
| CVE-2021-27212 | CRITICAL9.75 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u6 | 64.1% Actively Exploited | Directly Exposed |
| CVE-2019-9511 | CRITICAL9.75 | libnghttp2-14 1.36.0-2 fixed in 1.36.0-2+deb10u1 | 58.4% Actively Exploited | Directly Exposed |
| CVE-2019-9513 | CRITICAL9.75 | libnghttp2-14 1.36.0-2 fixed in 1.36.0-2+deb10u1 | 82.0% Actively Exploited | Directly Exposed |
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.36.0-2 fixed in 1.36.0-2+deb10u2 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2020-1967 | CRITICAL9.75 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u3 | 53.3% Actively Exploited | Directly Exposed |
| CVE-2021-23840 | CRITICAL9.75 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u5 | 50.7% Actively Exploited | Directly Exposed |
| CVE-2022-0778 | CRITICAL9.75 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u8 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libsystemd0 241-5 No fix yet | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-50868 | CRITICAL9.75 | libsystemd0 241-5 No fix yet | 81.7% Actively Exploited | Directly Exposed |
| CVE-2023-50387 | CRITICAL9.75 | libudev1 241-5 No fix yet | 100.0% Actively Exploited | Directly Exposed |
| CVE-2023-50868 | CRITICAL9.75 | libudev1 241-5 No fix yet | 81.7% Actively Exploited | Directly Exposed |
| CVE-2018-25032 | CRITICAL9.75 | zlib1g 1:1.2.11.dfsg-1 fixed in 1:1.2.11.dfsg-1+deb10u1 | 52.1% Actively Exploited | Directly Exposed |
| CVE-2021-3712 | CRITICAL9.62 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u7 | 50.4% Actively Exploited | Directly Exposed |
| CVE-2023-0286 | CRITICAL9.62 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u4 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2022-1292 | CRITICAL9.49 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u2 | 83.2% Actively Exploited | Directly Exposed |
| CVE-2022-2068 | CRITICAL9.49 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u3 | 95.8% Actively Exploited | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-35942 | CRITICAL9.1 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46848 | CRITICAL9.1 | libtasn1-6 4.13-3 fixed in 4.13-3+deb10u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45960 | HIGH8.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22825 | HIGH8.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22826 | HIGH8.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22827 | HIGH8.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssapi-krb5-2 1.17-3 fixed in 1.17-3+deb10u5 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10531 | HIGH8.8 | libicu63 63.1-6 fixed in 63.1-6+deb10u1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libk5crypto3 1.17-3 fixed in 1.17-3+deb10u5 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-3 1.17-3 fixed in 1.17-3+deb10u5 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5support0 1.17-3 fixed in 1.17-3+deb10u5 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1271 | HIGH8.8 | liblzma5 5.2.4-1 fixed in 5.2.4-1+deb10u1 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl2-2 2.1.27+dfsg-1 fixed in 2.1.27+dfsg-1+deb10u2 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl2-modules-db 2.1.27+dfsg-1 fixed in 2.1.27+dfsg-1+deb10u2 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3518 | HIGH8.8 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u2 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libgssapi-krb5-2 1.17-3 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libk5crypto3 1.17-3 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5-3 1.17-3 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2021-36222 | HIGH8.62 | libkrb5support0 1.17-3 fixed in 1.17-3+deb10u2 | 10.3% High Exploitation Risk | Directly Exposed |
| CVE-2020-36230 | HIGH8.62 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 12.3% High Exploitation Risk | Directly Exposed |
| CVE-2020-36230 | HIGH8.62 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 12.3% High Exploitation Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u4 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-40303 | HIGH8.62 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u5 | 22.8% High Exploitation Risk | Directly Exposed |
| CVE-2021-3517 | HIGH8.6 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u2 | 8.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13777 | HIGH8.51 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u4 | 17.5% High Exploitation Risk | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u5 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-6096 | HIGH8.1 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40674 | HIGH8.1 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u5 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libgcc1 1:8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20305 | HIGH8.1 | libhogweed4 3.4.1-1 fixed in 3.4.1-1+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-17543 | HIGH8.1 | liblz4-1 1.8.3-1 No fix yet | 9.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20305 | HIGH8.1 | libnettle6 3.4.1-1 fixed in 3.4.1-1+deb10u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-12886 | HIGH8.1 | libstdc++6 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25236 | HIGH8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 34.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-3711 | HIGH8 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u7 | 87.8% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2022-37434 | HIGH8 | zlib1g 1:1.2.11.dfsg-1 fixed in 1:1.2.11.dfsg-1+deb10u2 | 16.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22822 | HIGH7.84 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22823 | HIGH7.84 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22824 | HIGH7.84 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-1304 | HIGH7.8 | libcom-err2 1.44.5-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46143 | HIGH7.8 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libext2fs2 1.44.5-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libss2 1.44.5-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26604 | HIGH7.8 | libsystemd0 241-5 fixed in 241-7~deb10u9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-26604 | HIGH7.8 | libudev1 241-5 fixed in 241-7~deb10u9 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3516 | HIGH7.8 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u2 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40304 | HIGH7.8 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u5 | 6.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3449 | HIGH7.67 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u6 | 62.9% Actively Exploited | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3326 | HIGH7.5 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15903 | HIGH7.5 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u1 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23990 | HIGH7.5 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25314 | HIGH7.5 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43680 | HIGH7.5 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u6 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u7 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libgcc1 1:8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33560 | HIGH7.5 | libgcrypt20 1.8.4-5 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43618 | HIGH7.5 | libgmp10 2:6.1.2+dfsg-4 fixed in 2:6.1.2+dfsg-4+deb10u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24659 | HIGH7.5 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u7 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u9 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u12 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28196 | HIGH7.5 | libgssapi-krb5-2 1.17-3 fixed in 1.17-3+deb10u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3580 | HIGH7.5 | libhogweed4 3.4.1-1 fixed in 3.4.1-1+deb10u1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12290 | HIGH7.5 | libidn2-0 2.0.5-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28196 | HIGH7.5 | libk5crypto3 1.17-3 fixed in 1.17-3+deb10u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28196 | HIGH7.5 | libkrb5-3 1.17-3 fixed in 1.17-3+deb10u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-28196 | HIGH7.5 | libkrb5support0 1.17-3 fixed in 1.17-3+deb10u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12243 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u2 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25692 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25709 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u4 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25710 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36223 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36224 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36225 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36226 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36229 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13565 | HIGH7.5 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u1 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12243 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u2 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25692 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25709 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u4 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25710 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u4 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36223 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36224 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36225 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36226 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36229 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13565 | HIGH7.5 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u1 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3580 | HIGH7.5 | libnettle6 3.4.1-1 fixed in 3.4.1-1+deb10u1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11080 | HIGH7.5 | libnghttp2-14 1.36.0-2 fixed in 1.36.0-2+deb10u2 | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29361 | HIGH7.5 | libp11-kit0 0.23.15-2 fixed in 0.23.15-2+deb10u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29363 | HIGH7.5 | libp11-kit0 0.23.15-2 fixed in 0.23.15-2+deb10u1 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19906 | HIGH7.5 | libsasl2-2 2.1.27+dfsg-1 fixed in 2.1.27+dfsg-1+deb10u1 | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19906 | HIGH7.5 | libsasl2-modules-db 2.1.27+dfsg-1 fixed in 2.1.27+dfsg-1+deb10u1 | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u4 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u5 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15847 | HIGH7.5 | libstdc++6 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16932 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 5.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19956 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u1 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20388 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-7595 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u1 | 7.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2309 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23308 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u3 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14404 | HIGH7.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-11501 | HIGH7.4 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u3 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u10 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.36.0-2 fixed in 1.36.0-2+deb10u3 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u4 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2019-5094 | MEDIUM6.7 | libcom-err2 1.44.5-1 fixed in 1.44.5-1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5188 | MEDIUM6.7 | libcom-err2 1.44.5-1 fixed in 1.44.5-1+deb10u3 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5094 | MEDIUM6.7 | libext2fs2 1.44.5-1 fixed in 1.44.5-1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5188 | MEDIUM6.7 | libext2fs2 1.44.5-1 fixed in 1.44.5-1+deb10u3 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5094 | MEDIUM6.7 | libss2 1.44.5-1 fixed in 1.44.5-1+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5188 | MEDIUM6.7 | libss2 1.44.5-1 fixed in 1.44.5-1+deb10u3 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-3843 | MEDIUM6.63 | libsystemd0 241-5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2019-3844 | MEDIUM6.63 | libsystemd0 241-5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-1712 | MEDIUM6.63 | libsystemd0 241-5 fixed in 241-7~deb10u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-3843 | MEDIUM6.63 | libudev1 241-5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2019-3844 | MEDIUM6.63 | libudev1 241-5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-1712 | MEDIUM6.63 | libudev1 241-5 fixed in 241-7~deb10u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | libaprutil1 1.6.1-4 fixed in 1.6.1-4+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | libaprutil1-ldap 1.6.1-4 fixed in 1.6.1-4+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8927 | MEDIUM6.5 | libbrotli1 1.0.7-2 fixed in 1.0.7-2+deb10u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25313 | MEDIUM6.5 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u9 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libgssapi-krb5-2 1.17-3 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.17-3 fixed in 1.17-3+deb10u6 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libk5crypto3 1.17-3 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.17-3 fixed in 1.17-3+deb10u6 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5-3 1.17-3 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.17-3 fixed in 1.17-3+deb10u6 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37750 | MEDIUM6.5 | libkrb5support0 1.17-3 fixed in 1.17-3+deb10u3 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.17-3 fixed in 1.17-3+deb10u6 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14567 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u1 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3541 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29824 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u4 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-28484 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29469 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-18258 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24977 | MEDIUM6.5 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u2 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1551 | MEDIUM6.09 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u5 | 14.3% High Exploitation Risk | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc-bin 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc-dev-bin 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1751 | MEDIUM5.95 | libc6 2.28-10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-1752 | MEDIUM5.95 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.28-10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.28-10 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-dev-bin 2.28-10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-dev-bin 2.28-10 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10228 | MEDIUM5.9 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-25013 | MEDIUM5.9 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.28-10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.28-10 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-40528 | MEDIUM5.9 | libgcrypt20 1.8.4-5 fixed in 1.8.4-5+deb10u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u11 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-1971 | MEDIUM5.9 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u4 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-23841 | MEDIUM5.9 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u5 | 7.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4160 | MEDIUM5.9 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u8 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3537 | MEDIUM5.9 | libxml2 2.9.4+dfsg1-7+b3 fixed in 2.9.4+dfsg1-7+deb10u2 | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl1.1 1.1.1c-1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-3810 | MEDIUM5.5 | libapt-pkg5.0 1.8.2 fixed in 1.8.2.1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-21913 | MEDIUM5.5 | libicu63 63.1-6 fixed in 63.1-6+deb10u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1c-1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33910 | MEDIUM5.5 | libsystemd0 241-5 fixed in 241-7~deb10u8 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | libsystemd0 241-5 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33910 | MEDIUM5.5 | libudev1 241-5 fixed in 241-7~deb10u8 | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3997 | MEDIUM5.5 | libudev1 241-5 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9318 | MEDIUM5.5 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13627 | MEDIUM5.35 | libgcrypt20 1.8.4-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-29362 | MEDIUM5.3 | libp11-kit0 0.23.15-2 fixed in 0.23.15-2+deb10u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14155 | MEDIUM5.3 | libpcre3 2:8.39-12 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1549 | MEDIUM5.3 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u1 | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u4 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u6 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1c-1 fixed in 1.1.1n-0+deb10u6 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1c-1 No fix yet | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2016-3709 | MEDIUM5.18 | libxml2 2.9.4+dfsg1-7+b3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-10878 | MEDIUM5.16 | perl-base 5.28.1-6 fixed in 5.28.1-6+deb10u1 | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 241-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 241-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-13057 | MEDIUM4.9 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13057 | MEDIUM4.9 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22576 | MEDIUM4.86 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2019-17498 | MEDIUM4.86 | libssh2-1 1.8.0-2.1 fixed in 1.8.0-2.1+deb10u1 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.28.1-6 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2020-27350 | MEDIUM4.84 | libapt-pkg5.0 1.8.2 fixed in 1.8.2.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1c-1 No fix yet | 54.0% Actively Exploited | Directly Exposed |
| CVE-2019-1547 | MEDIUM4.7 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-8177 | MEDIUM4.68 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-37600 | MEDIUM4.67 | libblkid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-10029 | MEDIUM4.67 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-27618 | MEDIUM4.67 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libfdisk1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libmount1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libsmartcols1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libsystemd0 241-5 fixed in 241-7~deb10u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libsystemd0 241-5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libudev1 241-5 fixed in 241-7~deb10u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libudev1 241-5 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-37600 | MEDIUM4.67 | libuuid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-24031 | MEDIUM4.67 | libzstd1 1.3.8+dfsg-3 fixed in 1.3.8+dfsg-3+deb10u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-29155 | MEDIUM4.58 | libldap-2.4-2 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u7 | 69.9% Actively Exploited | Post-Exploit |
| CVE-2022-29155 | MEDIUM4.58 | libldap-common 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u7 | 69.9% Actively Exploited | Post-Exploit |
| CVE-2019-14855 | MEDIUM4.5 | gpgv 2.2.12-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8169 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8231 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8285 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 9.9% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8286 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 4.6% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2020-12723 | MEDIUM4.5 | perl-base 5.28.1-6 fixed in 5.28.1-6+deb10u1 | 6.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32206 | MEDIUM4.48 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 32.0% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libfdisk1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-5482 | MEDIUM4.06 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u1 | 17.9% High Exploitation Risk | Post-Exploit |
| CVE-2019-8457 | MEDIUM4.06 | libdb5.3 5.3.28+dfsg1-0.5 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2021-24032 | MEDIUM4 | libzstd1 1.3.8+dfsg-3 fixed in 1.3.8+dfsg-3+deb10u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-16156 | LOW3.98 | perl-base 5.28.1-6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-34903 | LOW3.9 | gpgv 2.2.12-1 fixed in 2.2.12-1+deb10u2 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u8 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2020-22218 | LOW3.82 | libssh2-1 1.8.0-2.1 fixed in 1.8.0-2.1+deb10u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2019-15718 | LOW3.74 | libsystemd0 241-5 fixed in 241-7~deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-15718 | LOW3.74 | libudev1 241-5 fixed in 241-7~deb10u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-1563 | LOW3.7 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u1 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-22947 | LOW3.54 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u4 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u6 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u7 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1664 | LOW3.53 | dpkg 1.19.7 fixed in 1.19.8 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33574 | LOW3.53 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23218 | LOW3.53 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33574 | LOW3.53 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33574 | LOW3.53 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2019-5481 | LOW3.53 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u1 | 7.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32221 | LOW3.53 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u4 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20231 | LOW3.53 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u7 | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20232 | LOW3.53 | libgnutls30 3.6.7-4 fixed in 3.6.7-4+deb10u7 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3520 | LOW3.53 | liblz4-1 1.8.3-1 fixed in 1.8.3-1+deb10u1 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u4 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2020-10543 | LOW3.4 | perl-base 5.28.1-6 fixed in 5.28.1-6+deb10u1 | 11.3% High Exploitation Risk | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-13115 | LOW3.35 | libssh2-1 1.8.0-2.1 fixed in 1.8.0-2.1+deb10u1 | 11.7% High Exploitation Risk | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 8.30-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-3810 | LOW3.3 | apt 1.8.2 fixed in 1.8.2.1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u6 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22876 | LOW3.18 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-7169 | LOW3.18 | passwd 1:4.5-1.1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | LOW3.17 | gzip 1.9-3 fixed in 1.9-3+deb10u1 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u6 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u9 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl4 7.64.0-4 No fix yet | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2020-27350 | LOW2.91 | apt 1.8.2 fixed in 1.8.2.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | bsdutils 1:2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | mount 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.5-1.1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-37600 | LOW2.8 | util-linux 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-19126 | LOW2.8 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19126 | LOW2.8 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-36084 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36085 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36086 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-36087 | LOW2.8 | libsepol1 2.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-8284 | LOW2.22 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22890 | LOW2.22 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u2 | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u4 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u8 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u7 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-27645 | LOW2.12 | libc-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-27645 | LOW2.12 | libc-dev-bin 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-27645 | LOW2.12 | libc6 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-22898 | LOW1.86 | libcurl4 7.64.0-4 fixed in 7.64.0-4+deb10u3 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.5-1.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.30+dfsg-6 fixed in 1.30+dfsg-6+deb10u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-33574 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-23218 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-23219 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-22822 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-22823 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-22824 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-23852 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-25235 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-25236 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 34.2% High Exploitation Risk | Not Applicable |
| CVE-2022-25315 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-29155 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u7 | 69.9% Actively Exploited | Not Applicable |
| CVE-2019-14895 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 7.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-14896 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 8.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-14897 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-14901 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 16.9% High Exploitation Risk | Not Applicable |
| CVE-2019-15504 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-15505 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-16746 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 12.7% High Exploitation Risk | Not Applicable |
| CVE-2019-17133 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 6.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-18805 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-18814 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-27068 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-25775 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2021-35942 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-15926 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-2961 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u3 | 88.3% Actively Exploited | Not Applicable |
| CVE-2021-45960 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-22825 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-22826 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-22827 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-10220 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-14821 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-17666 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-12351 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 7.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-29569 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-28660 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3653 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3656 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-0435 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 68.0% Actively Exploited | Not Applicable |
| CVE-2022-27223 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3640 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-42896 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-39537 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19770 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-1012 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-12886 | NONE0 | gcc-8-base 8.3.0-6 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-6096 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-40674 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u5 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2018-20836 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-9506 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-28374 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 6.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-4157 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1304 | NONE0 | e2fsprogs 1.44.5-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-3999 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-46143 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-0145 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-0155 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-13272 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u1 | 52.2% Actively Exploited | Not Applicable |
| CVE-2019-14814 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-14815 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-14816 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-14835 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-15117 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-15918 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-15925 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19252 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19377 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19447 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-19448 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19543 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-19816 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1999 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-25045 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-25162 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-0423 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-0444 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-0466 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-10757 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-12362 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-12653 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-12657 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-13974 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-14351 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-14356 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-14381 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-14386 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-16119 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25669 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-25670 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-25671 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-27786 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-27815 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-29661 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-35519 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-7053 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-0512 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-1048 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2021-22543 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-22555 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 78.7% Actively Exploited | Not Applicable |
| CVE-2021-26930 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.177-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-27365 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-29154 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-33033 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-33034 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3347 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-33631 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-33909 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-3 | 9.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3444 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3483 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-35039 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3600 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3612 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3715 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-37576 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3760 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-38160 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-38300 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-39634 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-39685 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-39698 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-41864 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4197 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-42008 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-42252 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4439 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-45469 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-46936 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46938 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46950 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46959 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46966 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46991 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46998 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46999 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47013 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47058 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47068 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47082 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47103 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47118 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47194 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47222 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47235 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47239 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47254 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47261 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47293 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47301 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47310 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47311 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47321 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47328 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47334 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47336 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47355 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47357 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47358 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47361 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47372 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47388 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47404 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47458 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47474 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47475 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47477 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47483 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47485 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47497 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47500 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47505 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47506 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47520 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47521 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47541 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47549 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47565 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47566 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47571 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47576 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47589 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47598 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47600 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47609 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0330 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0492 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-1011 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-1419 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1652 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-1679 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-20368 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-20421 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-20566 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-22942 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-24958 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2586 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 12.7% High Exploitation Risk | Not Applicable |
| CVE-2022-2588 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-2639 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-26490 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-27666 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-28390 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-29581 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-2964 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2977 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-2978 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-30594 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-32250 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-3239 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3424 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3545 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3565 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4095 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-4378 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-45934 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-4744 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-48626 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48672 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48695 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48702 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48717 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48732 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48742 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48771 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0386 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 7.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-0461 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-1078 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1118 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1281 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1670 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1829 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-2007 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-20938 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23559 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3090 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3111 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31436 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-32233 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 13.0% High Exploitation Risk | Not Applicable |
| CVE-2023-3390 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-34319 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-35001 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-35788 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3609 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3611 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3776 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3812 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-40283 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4206 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4207 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4208 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-42753 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4623 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4921 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-51042 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52436 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52439 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52444 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52445 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52451 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52464 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52469 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52475 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52510 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52594 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52599 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52600 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52603 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52604 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52612 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52679 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52691 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52764 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52796 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52799 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52804 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52805 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52818 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52835 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52836 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52840 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52864 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52867 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52868 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-5717 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-6040 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-1086 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 28.1% High Exploitation Risk | Not Applicable |
| CVE-2024-26625 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26704 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26754 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26793 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26883 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26884 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26898 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26934 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26955 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26956 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26957 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26965 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26981 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27000 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27008 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27024 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27043 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27075 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27395 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27396 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27398 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-35789 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35847 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35886 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36015 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36886 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-36904 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-36934 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36940 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36971 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2024-38552 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38578 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38583 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38627 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20669 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-10142 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-0432 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-32981 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u5 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-3900 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-33599 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-15847 | NONE0 | gcc-8-base 8.3.0-6 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3326 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-15903 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u1 | 6.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-23990 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u2 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-25314 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 4.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-43680 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u6 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52425 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u7 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-12243 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u2 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-25692 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u3 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-25709 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u4 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-25710 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u4 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-36221 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 84.2% Actively Exploited | Not Applicable |
| CVE-2020-36222 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 77.7% Actively Exploited | Not Applicable |
| CVE-2020-36223 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36224 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36225 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36226 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36227 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 77.7% Actively Exploited | Not Applicable |
| CVE-2020-36228 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 83.4% Actively Exploited | Not Applicable |
| CVE-2020-36229 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 4.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-36230 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u5 | 12.3% High Exploitation Risk | Not Applicable |
| CVE-2021-27212 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u6 | 64.1% Actively Exploited | Not Applicable |
| CVE-2023-2953 | NONE0 | libldap2-dev 2.4.47+dfsg-3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-13565 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u1 | 5.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-15099 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-15538 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2 | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-16714 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-17075 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-19048 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19052 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 5.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19071 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19074 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 4.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-19078 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 6.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-19079 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-19768 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-1749 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-25645 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-25672 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-38207 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 3.4% Low-Moderate Risk | Not Applicable |
| CVE-2021-45485 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1199 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-1678 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-36946 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 5.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-0045 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-1390 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-1 | 5.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45871 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-46838 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-52340 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-18813 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-19049 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-19060 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19061 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-19075 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-0136 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-2213 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-25705 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 6.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-20322 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 6.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-25643 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11668 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-12654 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-24394 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-36386 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-8428 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1+deb10u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-8648 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-9383 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-27364 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2021-3506 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3743 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3752 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-46955 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46992 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47153 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47160 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47240 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47243 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47245 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47277 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47288 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47309 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47346 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47383 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47393 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0850 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1353 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-26365 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3202 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-33740 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-33741 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-33742 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3564 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41858 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48701 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48738 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48757 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48760 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1380 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 16.6% High Exploitation Risk | Not Applicable |
| CVE-2023-1838 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3141 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3268 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3567 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4387 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52504 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52507 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52525 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52598 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52628 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-6606 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0775 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26597 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26664 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26763 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26791 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27401 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35849 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36883 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36960 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38381 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38560 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38599 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38621 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38659 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52502 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u3 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-1751 | NONE0 | libc6-dev 2.28-10 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-1752 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12817 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-13233 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-18683 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-11884 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1+deb10u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25212 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-25668 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-29368 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-29370 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-22600 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2021-23133 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-32399 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3348 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.177-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3609 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3640 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-39686 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-39713 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-40490 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4083 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-4202 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-44733 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47280 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1048 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1729 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1734 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-20141 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-20422 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-23036 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23037 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-23038 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23039 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23040 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23041 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-23042 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3028 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3635 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3649 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-48759 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0266 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-1077 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1989 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-28466 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-35823 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-35824 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-35828 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4244 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4622 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51043 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51780 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-51781 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-51782 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52578 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52847 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6270 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6931 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-6932 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26654 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26974 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27020 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26852 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45886 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45919 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-13631 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-14283 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-19527 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19531 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19532 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-0465 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-2732 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1+deb10u1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-33656 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-4203 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-1079 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-2002 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24857 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38204 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-5094 | NONE0 | e2fsprogs 1.44.5-1 fixed in 1.44.5-1+deb10u2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-5188 | NONE0 | e2fsprogs 1.44.5-1 fixed in 1.44.5-1+deb10u3 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-15090 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20636 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-20908 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.132-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-0431 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-12464 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-12465 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-12659 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-12770 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-15436 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2020-15780 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-27066 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-27777 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-36158 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-0342 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-0941 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-20292 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-28972 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-31916 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-33655 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-34981 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-39656 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-42739 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-43975 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-46953 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47356 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-20369 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-20572 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-21499 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-2503 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-43750 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-2194 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2513 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-28772 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-3159 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-32269 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2991 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3628 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1073 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0607 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14331 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-25147 | NONE0 | libaprutil1-dev 1.6.1-4 fixed in 1.6.1-4+deb10u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-25313 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u3 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-19185 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.1+20181013-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.1+20181013-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2018-12207 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-10638 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-11135 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u2 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-17351 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19319 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-3874 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-5108 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 10.1% High Exploitation Risk | Not Applicable |
| CVE-2020-12352 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 5.7% Low-Moderate Risk | Not Applicable |
| CVE-2020-13143 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 4.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-24490 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2020-29568 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-3702 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28038 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-28688 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28711 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28712 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28713 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28714 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28715 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3772 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-38199 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-0001 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0002 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-29900 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-29901 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-3621 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-3643 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-40982 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-2 | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-42895 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-30456 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3338 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 8.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19046 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-3178 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-1 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.1+20181013-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-19185 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19186 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-19187 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19188 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-19189 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2020-19190 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.1+20181013-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-0305 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-10690 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25285 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-0920 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3573 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-37159 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47274 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-20154 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-30772 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-33203 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45863 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36016 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19529 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1462 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1855 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52644 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24861 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-14284 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-30002 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19332 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-19528 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-10751 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-8647 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47478 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47547 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-39842 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-52810 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19927 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-11565 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1+deb10u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-25211 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-27171 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-47308 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2021-47548 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39189 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39192 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39193 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26894 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2016-10228 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 4.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-25013 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-4806 | NONE0 | libc6-dev 2.28-10 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | libc6-dev 2.28-10 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19080 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19081 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-10711 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2020-28097 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-36516 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-8649 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-28915 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-35910 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48651 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-27825 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-0129 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-1206 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-15902 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-14390 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-26401 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47375 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-23960 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-1998 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-48754 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-37600 | NONE0 | fdisk 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-10029 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-27618 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.3.1-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-0146 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-0147 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-0148 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-0149 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-0154 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-10207 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-12984 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-13648 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-14615 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-15118 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-2+deb10u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15924 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-18786 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-18885 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-19036 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19037 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2019-19039 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-19051 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-19077 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19227 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-19462 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19767 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19813 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19815 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19922 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-20054 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20095 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-20096 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2019-20810 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20812 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-0009 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-0404 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-0427 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-0543 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-10720 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-10766 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-10767 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-10768 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-10781 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-11669 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-12363 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12364 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12655 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-12768 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-12769 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-12771 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14314 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-14385 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-15393 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25641 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-25673 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-25704 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-26088 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-27673 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-27784 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-27830 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-28941 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36311 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36312 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36322 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-36777 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-8694 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-8992 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-20320 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-26931 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26932 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.177-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-28950 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-28971 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-29155 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-29264 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-29647 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-29650 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-31829 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33098 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33630 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3428 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-34556 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-34693 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-35477 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3564 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3659 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3679 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3732 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3744 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3764 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38198 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-38208 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-39633 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4135 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4149 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4155 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-43389 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-44879 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-45095 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-45480 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-45868 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-46904 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46906 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46909 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46915 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46921 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46924 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46929 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46932 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46933 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46935 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46939 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46960 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46963 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46974 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46985 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46988 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-46990 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47020 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47054 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47055 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47056 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47073 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47086 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47100 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47104 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47117 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47121 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47122 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47142 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47145 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47146 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47149 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47150 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47159 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47162 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47165 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47166 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47168 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47169 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47170 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47171 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47173 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47177 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47179 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47180 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47181 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47184 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47189 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-47203 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47206 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47207 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47210 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47216 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47217 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47223 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47229 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47236 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47237 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47249 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47250 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47252 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47256 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47258 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47260 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47269 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47270 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47276 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47294 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47296 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47305 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47314 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47315 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47319 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47320 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47323 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-47330 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47337 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47340 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47343 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47344 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47345 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47347 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-47353 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47373 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47387 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47395 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47397 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47401 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47405 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47409 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47416 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47418 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47423 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47424 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47425 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47434 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47436 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47442 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47445 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47460 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47468 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47480 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47495 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47499 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47509 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47511 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47515 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47516 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47518 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47527 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47538 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47542 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47579 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47583 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47587 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47588 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47602 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47606 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47611 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47612 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47617 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.235-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47619 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47620 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0322 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0480 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0487 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0617 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-0854 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-1016 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1195 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1198 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1204 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1516 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1975 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-21123 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 6.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-21125 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-21166 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 5.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-2153 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2318 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-2380 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-24959 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-25375 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-26373 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-26966 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-28356 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-28388 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-28389 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2873 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3107 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3111 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3524 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-3586 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-36280 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-36879 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3707 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-40768 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-41218 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-42328 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-42329 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-42703 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-4662 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-47929 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-48619 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48629 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48630 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48636 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48641 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48659 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48671 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48687 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48688 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48693 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48704 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48708 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48710 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48711 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48715 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48722 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48724 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48743 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-48756 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-48758 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0394 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-0459 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-0615 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1074 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1095 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1637 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20593 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-2162 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-23454 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23455 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-28328 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2985 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3006 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31084 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3161 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3220 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3358 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-34256 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-42754 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-42755 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4385 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4459 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45862 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-46343 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52429 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52443 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52449 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52470 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52477 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52486 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52527 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52528 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52566 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52567 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52574 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52577 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52583 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52587 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52601 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52606 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52607 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52615 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52619 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52622 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52623 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52646 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52650 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52670 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52675 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52683 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52686 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52693 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52698 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52699 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-52703 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52705 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52730 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52742 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52747 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52753 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52774 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52789 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52806 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52809 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52813 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52817 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52832 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-52843 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52845 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52853 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52865 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52875 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52880 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52881 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-7042 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-0340 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0639 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-22099 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-23848 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23849 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-23851 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25739 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26600 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26602 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26606 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26615 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26635 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26636 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26642 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26645 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26651 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26663 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26675 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26679 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26696 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26697 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26722 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26735 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26744 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26751 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26752 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26766 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26772 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26773 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26777 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26778 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26779 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26801 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26805 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26816 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26817 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26820 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26825 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26839 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26840 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26845 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26851 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26863 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26880 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-26889 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26901 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26903 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26917 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26922 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26931 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26966 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26969 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26973 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26976 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26984 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26993 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26994 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26997 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26999 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27001 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27013 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27028 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-27046 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27059 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27074 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27077 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27078 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27388 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27399 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27405 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-27410 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27412 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27413 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27416 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27436 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-31076 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-33621 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35806 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35807 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35811 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35815 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35819 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35821 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-35822 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35823 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35825 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35828 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35830 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35835 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-35877 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35893 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35898 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35902 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35915 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35922 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35925 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35930 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35933 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35936 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35944 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35955 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-35960 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-35969 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35978 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35982 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35984 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35997 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36004 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36014 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36017 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36020 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36286 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36288 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36902 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36905 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36919 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36933 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36941 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36946 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36954 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36959 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36964 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-37356 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38549 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38558 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38565 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-38567 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38579 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38582 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-38587 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-38589 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38598 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38607 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38612 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-38618 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-38633 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38634 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38637 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38661 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38780 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39292 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39301 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-18806 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-18808 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-12656 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.131-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-0938 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-47114 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47257 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47259 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-47267 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-47284 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47297 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47403 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47443 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47456 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47482 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-48697 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52819 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26633 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26685 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35888 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35947 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-35973 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-39276 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-4641 | NONE0 | login 1:4.5-1.1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-37600 | NONE0 | uuid-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-17595 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2020-26147 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 7.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-17595 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-33600 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-17594 | NONE0 | libncursesw6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17594 | NONE0 | libtinfo6 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-18282 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-20934 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-10942 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1+deb10u1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-12826 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-12888 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-26139 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 6.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-47238 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-2663 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-3594 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-24858 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-7169 | NONE0 | login 1:4.5-1.1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses-base 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17594 | NONE0 | ncurses-bin 6.1+20181013-2 fixed in 6.1+20181013-2+deb10u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-36557 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36558 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47231 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-28974 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-13057 | NONE0 | libldap2-dev 2.4.47+dfsg-3 fixed in 2.4.47+dfsg-3+deb10u1 | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-34324 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-15807 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-18660 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-19056 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19058 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19059 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19062 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-19065 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19066 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19082 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19965 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-3016 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-12114 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-27170 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-27675 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-4788 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-20321 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-28964 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-29265 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-33624 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-3753 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-47248 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47435 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1205 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-33744 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-39188 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-40307 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41850 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-0458 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-0590 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1382 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1859 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-1990 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-20569 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 6.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-26545 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52478 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52602 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52609 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-22386 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26671 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26859 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26874 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26878 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26923 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27419 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35809 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38596 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38601 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38613 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-19054 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-45887 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-15098 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-15211 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15212 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15215 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15216 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-15217 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-15218 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15219 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-15220 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-15221 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-15291 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-18809 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19068 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19523 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19524 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-19525 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19526 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19530 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19535 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19536 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19947 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19966 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-23134 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-43976 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-20008 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-20132 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-20423 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-25258 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-19063 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2020-35508 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-28085 | NONE0 | fdisk 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-15030 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-15031 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-15666 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19045 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-19072 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19318 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-20806 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-9445 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-9453 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-0067 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-10732 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-2+deb10u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2020-10773 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-11494 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-15437 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-27418 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-29660 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-0605 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.152-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-20177 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-20317 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-27363 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.181-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2021-3635 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-39657 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4002 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-4159 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47006 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47078 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47324 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-47603 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0494 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-48627 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-2269 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.289-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-2860 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3212 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3772 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-39194 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-7192 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-36950 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19067 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-47010 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-47034 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47161 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47185 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47440 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-47476 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52838 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52855 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.304-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26857 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26875 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38559 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-28085 | NONE0 | uuid-dev 2.33.1-0.1 fixed in 2.33.1-0.1+deb10u1 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-15920 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.67-1 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-11608 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-11609 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-0812 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3646 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-47233 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19537 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-14416 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.118-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-26558 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2022-41849 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-12652 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-25284 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-25656 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.160-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-39648 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.171-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1974 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12614 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-33601 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-33602 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19073 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52597 | NONE0 | linux-libc-dev 4.19.37-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-16166 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-29374 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-24586 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2020-24588 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2021-45486 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19126 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-17052 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-17053 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17054 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17055 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-17056 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-19057 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.98-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-29371 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-36766 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.146-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-21781 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.177-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3655 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38205 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.208-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-38209 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-46934 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-24448 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-32296 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-33981 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.249-2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-3629 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.260-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-1513 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.282-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26764 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35935 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.5-1.1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-24587 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.194-1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-27645 | NONE0 | libc6-dev 2.28-10 fixed in 2.28-10+deb10u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3521 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.269-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52620 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.316-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-19533 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19534 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.87-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3923 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.232-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-1125 | NONE0 | linux-libc-dev 4.19.37-5 fixed in 4.19.37-5+deb10u2 | 4.5% Low-Moderate Risk | Not Applicable |
| DLA-3482-1 | NONE0 | debian-archive-keyring 2019.1 fixed in 2019.1+deb10u2 | — | Not Applicable |
| DLA-3112-1 | NONE0 | libbz2-1.0 1.0.6-9.1 fixed in 1.0.6-9.2~deb10u2 | — | Not Applicable |
| DSA-5085-2 | NONE0 | libexpat1 2.2.6-2 fixed in 2.2.6-2+deb10u4 | — | Not Applicable |
| DSA-5085-2 | NONE0 | libexpat1-dev 2.2.6-2 fixed in 2.2.6-2+deb10u4 | — | Not Applicable |
| DSA-4539-3 | NONE0 | libssl1.1 1.1.1c-1 fixed in 1.1.1d-0+deb10u2 | — | Not Applicable |
| DLA-3134-1 | NONE0 | tzdata 2019a-1 fixed in 2021a-0+deb10u7 | — | Not Applicable |
| DLA-3161-1 | NONE0 | tzdata 2019a-1 fixed in 2021a-0+deb10u8 | — | Not Applicable |
| DLA-3366-1 | NONE0 | tzdata 2019a-1 fixed in 2021a-0+deb10u10 | — | Not Applicable |
| DLA-3412-1 | NONE0 | tzdata 2019a-1 fixed in 2021a-0+deb10u11 | — | Not Applicable |
| DLA-3684-1 | NONE0 | tzdata 2019a-1 fixed in 2021a-0+deb10u12 | — | Not Applicable |
| DLA-3788-1 | NONE0 | tzdata 2019a-1 fixed in 2024a-0+deb10u1 | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.