New vulnerabilities in glib2, libssh, etc are present in nf-launcher and therefore in tower-backend images too.
A yum update (already part of the nf-launcher Dockerfile), should fix most of them:
[alberto@fedora]$ podman run --rm -it --entrypoint bash quay.io/seqeralabs/nf-launcher:j17-22.10.8
bash-4.2# yum update
===========================================================================================
Package Arch Version Repository Size
===========================================================================================
Updating:
ca-certificates noarch 2021.2.50-72.amzn2.0.7 amzn2-core 370 k
gd x86_64 2.0.35-27.amzn2.0.1 amzn2-core 146 k
glib2 x86_64 2.56.1-9.amzn2.0.3 amzn2-core 2.4 M
glibc x86_64 2.26-63.amzn2 amzn2-core 3.3 M
glibc-common x86_64 2.26-63.amzn2 amzn2-core 774 k
glibc-langpack-en x86_64 2.26-63.amzn2 amzn2-core 289 k
glibc-minimal-langpack x86_64 2.26-63.amzn2 amzn2-core 33 k
jasper-libs x86_64 1.900.1-33.amzn2.0.1 amzn2-core 146 k
java-17-amazon-corretto-devel x86_64 1:17.0.7.7-1 AmazonCorretto 185 M
libcrypt x86_64 2.26-63.amzn2 amzn2-core 53 k
libgs x86_64 9.25-5.amzn2.0.3 amzn2-core 4.5 M
libssh2 x86_64 1.4.3-12.amzn2.2.4 amzn2-core 136 k
libxml2 x86_64 2.9.1-6.amzn2.5.8 amzn2-core 661 k
openldap x86_64 2.4.44-25.amzn2.0.5 amzn2-core 351 k
python2-rpm x86_64 4.11.3-48.amzn2.0.3 amzn2-core 85 k
rpm x86_64 4.11.3-48.amzn2.0.3 amzn2-core 1.2 M
rpm-build-libs x86_64 4.11.3-48.amzn2.0.3 amzn2-core 107 k
rpm-libs x86_64 4.11.3-48.amzn2.0.3 amzn2-core 277 k
tzdata noarch 2023c-1.amzn2.0.1 amzn2-core 482 k
vim-data noarch 2:9.0.1403-1.amzn2.0.2 amzn2-core 79 k
vim-minimal x86_64 2:9.0.1403-1.amzn2.0.2 amzn2-core 742 k
===========================================================================================
The only vulnerability left over then is in jline, a java package:
Java (jar)
Total: 1 (UNKNOWN: 0, LOW: 0, MEDIUM: 1, HIGH: 0, CRITICAL: 0)
┌─────────────────────────────┬───────────────┬──────────┬───────────────────┬───────────────┬────────────────────────────────────────────────────────────┐
│ Library │ Vulnerability │ Severity │ Installed Version │ Fixed Version │ Title │
├─────────────────────────────┼───────────────┼──────────┼───────────────────┼───────────────┼────────────────────────────────────────────────────────────┤
│ jline:jline (jline-2.9.jar) │ CVE-2013-2035 │ MEDIUM │ 2.9 │ 2.11 │ predictable temporary file name leading to local arbitrary │
│ │ │ │ │ │ code execution │
│ │ │ │ │ │ https://avd.aquasec.com/nvd/cve-2013-2035 │
└─────────────────────────────┴───────────────┴──────────┴───────────────────┴───────────────┴────────────────────────────────────────────────────────────┘
New vulnerabilities in glib2, libssh, etc are present in nf-launcher and therefore in tower-backend images too.
A
yum update(already part of the nf-launcher Dockerfile), should fix most of them:The only vulnerability left over then is in jline, a java package: