registry.redhat.io/ocp-tools-4/jenkins-rhel8:v4.12.0-1723557810

With RPM updates as of

Show kernel-headers

ID	Age	Component	Trivy Severity	Grype Severity	Red Hat Severity	Scandy Opinion
CVE-2025-21613	85	github.com/go-git/go-git/v5	Critical	Critical	Important
CVE-2024-45337	111	golang.org/x/crypto	Critical	Critical	Important
CVE-2024-41110	253	github.com/docker/docker	Critical	Critical	Critical	False Positive
CVE-2024-38821	155	org.springframework.security:spring-security-web spring-security-web	Critical	Critical	Moderate
CVE-2024-24790	302	git-lfs stdlib	Critical	Critical	Moderate
CVE-2024-23653	427	github.com/moby/buildkit	Critical	Critical	Important	False Positive
CVE-2024-23652	427	github.com/moby/buildkit	Critical	Critical	Important	False Positive
CVE-2023-49569	449	github.com/go-git/go-git/v5	Critical	Critical	Critical	False Positive
CVE-2016-1000027	3190	org.springframework:spring-web spring-web	Critical	Critical	Moderate	Ignorable
CVE-2025-30204	11	github.com/golang-jwt/jwt/v4	High	High	Important
CVE-2025-27363	21	freetype	High	High	Important
CVE-2025-24928	43	libxml2 python3-libxml2	High	High	Important
CVE-2025-24855	19	libxslt	High	High	Important
CVE-2025-22228	12	org.springframework.security:spring-security-crypto spring-security-crypto	High	High	Important
CVE-2025-21614	85	github.com/go-git/go-git/v5	High	High	Important
CVE-2025-1244	49	emacs-filesystem	High	High	Important	Ignorable
CVE-2025-0624	42	grub2-common grub2-tools grub2-tools-minimal	High	High	Important
CVE-2024-56171	43	libxml2 python3-libxml2	High	High	Important
CVE-2024-55549	19	libxslt	High	High	Important
CVE-2024-53263	77	git-lfs	High	High	Important
CVE-2024-52531	142	libsoup	High	High	Important
CVE-2024-52530	142	libsoup	High	High	Important
CVE-2024-47072	145	com.thoughtworks.xstream:xstream xstream	High	High	Important
CVE-2024-34156	207	git-lfs stdlib	High	High	Important
CVE-2024-23651	427	github.com/moby/buildkit	High	High	Moderate	False Positive
CVE-2024-21626	426	github.com/opencontainers/runc	High	High	Important	False Positive
CVE-2024-12085	77	rsync	High	High	Important
CVE-2024-11187	63	bind-libs bind-libs-lite bind-license bind-utils python3-bind	High	High	Important
CVE-2024-10963	146	pam	High	High	Important
CVE-2024-6345	261	platform-python-setuptools python3-setuptools python3-setuptools-wheel	High	High	Important
CVE-2024-3727	328	github.com/containers/image/v5	High	High	Moderate
CVE-2024-3596	267	krb5-libs	High	High	Important
CVE-2024-1975	253	bind-libs bind-libs-lite bind-license bind-utils python3-bind	High	High	Important
CVE-2024-1737	253	bind-libs bind-libs-lite bind-license bind-utils python3-bind	High	High	Important
CVE-2024-1488	414	python3-unbound unbound-libs	High		Important
CVE-2023-49568	465	github.com/go-git/go-git/v5	High	High	Important
CVE-2023-45288	364	golang.org/x/net stdlib	High	High	Important
CVE-2023-45287	484	stdlib	High	High	Moderate
CVE-2023-45283	509	stdlib	High
CVE-2023-39325	540	golang.org/x/net stdlib	High	High	Important
CVE-2023-28840	729	github.com/docker/docker	High	High	Important
CVE-2023-27561	772	github.com/opencontainers/runc	High	High	Moderate
CVE-2023-2253	693	github.com/docker/distribution	High	High	Moderate
CVE-2022-37967	838	krb5-libs	High		Important
CVE-2022-23648	1127	github.com/containerd/containerd	High	High	Important
CVE-2021-43816	1183	github.com/containerd/containerd	High	High	Important
GHSA-xmmx-7jpf-fx42	295	github.com/docker/docker	Medium	Medium
GHSA-jq35-85cj-fj4p	519	github.com/docker/docker	Medium	Medium
GHSA-7ww5-4wqc-m92c	469	github.com/containerd/containerd	Medium	Medium
CVE-2025-27625	27	org.jenkins-ci.main:jenkins-core	Medium		Moderate
CVE-2025-27624	27	org.jenkins-ci.main:jenkins-core	Medium		Moderate
CVE-2025-27623	27	org.jenkins-ci.main:jenkins-core	Medium		Moderate
CVE-2025-27622	27	org.jenkins-ci.main:jenkins-core	Medium		Moderate
CVE-2025-25724	31	libarchive	Medium	Medium	Moderate
CVE-2025-24528	430	krb5-libs	Medium	Medium	Moderate
CVE-2025-22870	20	git-lfs golang.org/x/net	Medium	Medium	Moderate
CVE-2025-22866	54	git-lfs stdlib	Medium	Medium	Moderate
CVE-2025-1118	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2025-0938	60	platform-python python3-libs python36	Medium	Medium	Moderate
CVE-2025-0690	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2025-0677	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2025-0622	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2025-0395	69	glibc glibc-common glibc-gconv-extra glibc-langpack-en glibc-locale-source glibc-minimal-langpack	Medium	Medium	Moderate
CVE-2024-57970	45	libarchive	Medium	Medium	Moderate
CVE-2024-56738	94	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-53920	126	emacs-filesystem	Medium	Medium	Moderate	Ignorable
CVE-2024-52616	138	avahi-libs	Medium	Medium	Moderate
CVE-2024-52615	138	avahi-libs	Medium	Medium	Moderate
CVE-2024-52533	142	glib2	Medium	Medium	Moderate
CVE-2024-52532	142	libsoup	Medium	Medium	Moderate
CVE-2024-52005	76	git git-core git-core-doc perl-Git	Medium	Medium	Moderate
CVE-2024-50602	157	expat	Medium	Medium	Moderate
CVE-2024-47804	181	org.jenkins-ci.main:jenkins-core	Medium		Moderate
CVE-2024-47803	181	org.jenkins-ci.main:jenkins-core	Medium		Moderate
CVE-2024-45783	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-45781	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-45777	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-45776	42	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-45775	64	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-45774	43	grub2-common grub2-tools grub2-tools-minimal	Medium	Medium	Moderate
CVE-2024-45492	215	expat	Medium	Medium	Moderate
CVE-2024-45491	215	expat	Medium	Medium	Moderate
CVE-2024-45490	215	expat	Medium	Medium	Moderate
CVE-2024-45341	75	git-lfs stdlib	Medium	Medium	Low
CVE-2024-45336	75	git-lfs stdlib	Medium	Medium	Moderate
CVE-2024-45310	210	github.com/opencontainers/runc	Medium	Medium	Low
CVE-2024-40635	15	github.com/containerd/containerd	Medium	Medium	Moderate
CVE-2024-39331	283	emacs-filesystem	Medium	Medium	Moderate	Ignorable
CVE-2024-38827	120	org.springframework.security:spring-security-core spring-security-core	Medium	Medium	Moderate
CVE-2024-38820	165	org.springframework:spring-context spring-context	Medium	Medium
CVE-2024-38809	189	org.springframework:spring-web spring-web	Medium	Medium	Moderate
CVE-2024-38808	225	org.springframework:spring-expression spring-expression	Medium	Medium	Moderate
CVE-2024-38428	305	wget	Medium	Medium	Moderate
CVE-2024-37891	289	python3-urllib3	Medium	Medium	Moderate
CVE-2024-37371	279	krb5-libs	Medium	Medium	Moderate
CVE-2024-37370	279	krb5-libs	Medium	Medium	Moderate
CVE-2024-35195	317	python3-requests	Medium	Medium	Moderate
CVE-2024-34397	330	glib2	Medium	Medium	Moderate
CVE-2024-34158	207	stdlib	Medium	High	Moderate
CVE-2024-34155	207	stdlib	Medium	Medium	Moderate
CVE-2024-30205	373	emacs-filesystem	Medium	Medium	Moderate	Ignorable
CVE-2024-30204	373	emacs-filesystem	Medium	Medium	Moderate	Ignorable
CVE-2024-30203	373	emacs-filesystem	Medium	Medium	Moderate	Ignorable
CVE-2024-29018	378	github.com/docker/docker	Medium		Moderate
CVE-2024-24791	274	git-lfs stdlib	Medium	High	Moderate
CVE-2024-24789	302	stdlib	Medium	Medium	Moderate
CVE-2024-24786	393	google.golang.org/protobuf	Medium	Medium	Moderate
CVE-2024-24785	393	stdlib	Medium	Medium	Moderate
CVE-2024-24784	393	stdlib	Medium	High	Moderate
CVE-2024-24783	393	stdlib	Medium	Medium	Moderate
CVE-2024-24557	426	github.com/docker/docker	Medium	Medium	Moderate
CVE-2024-23650	427	github.com/moby/buildkit	Medium	Medium	Moderate	False Positive
CVE-2024-21235	168	java-1.8.0-openjdk java-1.8.0-openjdk-devel java-1.8.0-openjdk-headless java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless	Medium	Medium	Moderate
CVE-2024-21217	168	java-1.8.0-openjdk java-1.8.0-openjdk-devel java-1.8.0-openjdk-headless java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless	Medium	Medium	Moderate
CVE-2024-21210	168	java-1.8.0-openjdk java-1.8.0-openjdk-devel java-1.8.0-openjdk-headless java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless	Medium	Medium	Moderate
CVE-2024-21208	168	java-1.8.0-openjdk java-1.8.0-openjdk-devel java-1.8.0-openjdk-headless java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless	Medium	Medium	Moderate
CVE-2024-12747	77	rsync	Medium	Medium	Moderate
CVE-2024-12243	51	gnutls libtasn1	Medium	Medium	Moderate
CVE-2024-12133	51	libtasn1	Medium	Medium	Moderate
CVE-2024-12088	77	rsync	Medium	Medium	Moderate
CVE-2024-12087	77	rsync	Medium	Medium	Moderate
CVE-2024-12086	77	rsync	Medium	Medium	Moderate
CVE-2024-11168	140	platform-python python3-libs	Medium	Medium	Moderate
CVE-2024-10524	133	wget	Medium	Medium	Moderate
CVE-2024-10041	166	pam	Medium	Medium	Moderate
CVE-2024-9287	161	platform-python python3-libs	Medium	Medium	Moderate
CVE-2024-8508	180	python3-unbound unbound-libs	Medium	Medium	Moderate
CVE-2024-8184	169	jetty-server org.eclipse.jetty:jetty-server	Medium	Medium	Moderate
CVE-2024-8176	19	expat	Medium	Medium	Moderate
CVE-2024-8088	222	python36	Medium	Medium	Moderate
CVE-2024-7006	257	libtiff	Medium	Medium	Moderate
CVE-2024-6923	244	platform-python python3-libs	Medium	Medium	Moderate
CVE-2024-6763	169	jetty-http org.eclipse.jetty:jetty-http	Medium	Medium	Low
CVE-2024-6655	291	gtk-update-icon-cache gtk2 gtk3	Medium	Medium	Moderate
CVE-2024-6602	267	nss nss-softokn nss-softokn-freebl nss-sysinit nss-util	Medium	Medium	Moderate
CVE-2024-6232	210	platform-python python3-libs	Medium	Medium	Moderate
CVE-2024-2398	371	curl libcurl	Medium	Medium	Moderate
CVE-2023-52355	516	libtiff	Medium	Medium	Moderate
CVE-2023-51767	465	openssh openssh-clients	Medium	Medium	Moderate	Removable
CVE-2023-48795	471	golang.org/x/crypto	Medium	Medium	Moderate
CVE-2023-48161	497	java-1.8.0-openjdk java-1.8.0-openjdk-devel java-1.8.0-openjdk-headless java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless	Medium	Medium	Moderate
CVE-2023-45290	393	stdlib	Medium	Medium	Moderate
CVE-2023-45289	393	stdlib	Medium	Medium	Moderate
CVE-2023-45284	509	stdlib	Medium
CVE-2023-44487	540	golang.org/x/net google.golang.org/grpc stdlib	Medium	High	Important
CVE-2023-41175	621	libtiff	Medium	Medium	Moderate
CVE-2023-40745	621	libtiff	Medium	Medium	Moderate
CVE-2023-40403	553	libxslt	Medium	Medium	Moderate
CVE-2023-39326	483	stdlib	Medium	Medium	Moderate
CVE-2023-39322	574	git-lfs	Medium	Medium	Moderate
CVE-2023-39321	574	git-lfs	Medium	Medium	Moderate
CVE-2023-39319	574	stdlib	Medium	Medium	Moderate
CVE-2023-39318	574	stdlib	Medium	Medium	Moderate
CVE-2023-30775	716	libtiff	Medium	Medium	Moderate
CVE-2023-30774	716	libtiff	Medium	Medium	Moderate
CVE-2023-30086	693	libtiff	Medium	Medium	Moderate
CVE-2023-28842	729	github.com/docker/docker	Medium	Medium	Moderate
CVE-2023-28841	729	github.com/docker/docker	Medium	Medium	Moderate
CVE-2023-28642	735	github.com/opencontainers/runc	Medium	Medium	Moderate
CVE-2023-26966	777	libtiff	Medium	Medium	Moderate
CVE-2023-26965	658	libtiff	Medium	Medium	Moderate
CVE-2023-25435	796	libtiff	Medium	Medium	Moderate
CVE-2023-25434	658	libtiff	Medium	Medium	Moderate
CVE-2023-25173	777	github.com/containerd/containerd	Medium	Medium	Moderate
CVE-2023-25153	777	github.com/containerd/containerd	Medium	Medium	Moderate
CVE-2023-7207	454	cpio	Medium	Medium	Moderate
CVE-2023-6277	517	libtiff	Medium	Medium	Moderate
CVE-2023-5455	447	krb5-libs	Medium	Medium	Moderate
CVE-2023-4504	559	cups-libs	Medium	Medium	Moderate
CVE-2023-3978	609	golang.org/x/net	Medium	Medium	Moderate
CVE-2023-3618	779	libtiff	Medium	Medium	Moderate
CVE-2023-3576	757	libtiff	Medium	Medium	Moderate
CVE-2023-3316	653	libtiff	Medium	Medium	Moderate
CVE-2023-3164	730	libtiff	Medium	Medium	Moderate
CVE-2023-0799	780	libtiff	Medium	Medium	Moderate
CVE-2023-0798	780	libtiff	Medium	Medium	Moderate
CVE-2023-0797	780	libtiff	Medium	Medium	Moderate
CVE-2023-0796	780	libtiff	Medium	Medium	Moderate
CVE-2023-0795	780	libtiff	Medium	Medium	Moderate
CVE-2023-0466	736	openssl openssl-libs	Medium	Medium	Moderate
CVE-2022-49043	66	libxml2 python3-libxml2	Medium	Medium	Moderate
CVE-2022-48338	771	emacs-filesystem	Medium	Medium	Moderate	Ignorable
CVE-2022-40090	954	libtiff	Medium	Medium	Moderate
CVE-2022-36109	930	github.com/docker/docker	Medium	Medium	Low
CVE-2022-31030	1027	github.com/containerd/containerd	Medium	Medium
CVE-2022-29162	1055	github.com/opencontainers/runc	Medium	Medium	Low
CVE-2022-24769	1106	github.com/docker/docker	Medium	Medium	Moderate
CVE-2022-23990	1162	expat	Medium	Medium	Moderate
CVE-2022-23471	846	github.com/containerd/containerd	Medium	Medium
CVE-2022-3599	1132	libtiff	Medium	Medium	Moderate
CVE-2022-3598	1024	libtiff	Medium	Medium	Moderate
CVE-2022-3570	1133	libtiff	Medium	Medium	Moderate
CVE-2022-3554	898	libX11 libX11-common	Medium	Medium	Moderate	Ignorable
CVE-2022-2963	987	jasper-libs	Medium	Medium	Moderate
CVE-2021-45941	1187	libbpf	Medium	Medium	Moderate
CVE-2021-45940	1187	libbpf	Medium	Low	Low
CVE-2021-43784	1213	github.com/opencontainers/runc	Medium	Medium	Low
CVE-2021-41103	1276	github.com/containerd/containerd	Medium	Medium	Moderate
CVE-2021-41091	1276	github.com/docker/docker	Medium	Medium	Moderate
CVE-2021-36217	1365	avahi-libs	Medium		Moderate
CVE-2021-33294	624	elfutils-debuginfod-client elfutils-default-yama-scope elfutils-libelf elfutils-libs	Medium	Medium	Moderate
CVE-2021-32760	1353	github.com/containerd/containerd	Medium	Medium	Moderate
CVE-2021-31879	2007	wget	Medium	Medium	Moderate
CVE-2021-3733	1331	python36	Medium	Medium	Moderate
CVE-2021-3467	1492	jasper-libs	Medium	Medium	Moderate
CVE-2021-3443	1482	jasper-libs	Medium	Medium	Moderate
CVE-2020-36843	19	eddsa net.i2p.crypto:eddsa	Medium	Medium
CVE-2020-26154	1721	libproxy	Medium	Medium	Moderate
CVE-2020-25219	1666	libproxy	Medium	Medium	Moderate
CVE-2020-17049	1604	krb5-libs	Medium	Medium	Moderate
CVE-2020-13790	1773	libjpeg-turbo	Medium	Medium	Moderate
CVE-2020-13645	1794	glib-networking	Medium	Medium	Moderate
CVE-2020-11023	1799	libgcc libgomp libstdc++	Medium	Medium	Moderate
CVE-2019-12900	137	bzip2 bzip2-libs	Medium	Medium	Moderate
CVE-2019-8905	2235	file file-libs	Medium	Medium	Moderate
CVE-2019-6462	2273	cairo cairo-gobject	Medium	Medium	Moderate
CVE-2019-6461	2273	cairo cairo-gobject	Medium	Medium	Moderate
CVE-2019-6128	2280	libtiff	Medium	Medium	Moderate
CVE-2019-6110	2329	openssh openssh-clients	Medium	Medium	Moderate	Removable
CVE-2019-2201	2098	libjpeg-turbo	Medium	Medium	Moderate
CVE-2018-1000021	2643	git git-core git-core-doc perl-Git	Medium	Medium	Moderate
CVE-2018-20839	2147	systemd systemd-libs systemd-pam systemd-udev	Medium	Medium	Moderate
CVE-2018-19217	2333	ncurses ncurses-base ncurses-libs	Medium	Medium	Moderate
CVE-2018-18064	2368	cairo cairo-gobject	Medium	Medium	Moderate
CVE-2018-16435	2424	lcms2	Medium	Medium	Moderate
CVE-2018-16335	2430	libtiff	Medium	Medium	Moderate
CVE-2018-15919	2409	openssh openssh-clients	Medium	Medium	Moderate	Removable
CVE-2018-10801	2522	libtiff	Medium	Medium	Moderate
CVE-2018-9252	2557	jasper-libs	Medium	Medium	Moderate
CVE-2018-9055	2564	jasper-libs	Medium	Medium	Moderate
CVE-2017-17095	2681	libtiff	Medium	Medium	Moderate
CVE-2017-5505	3055	jasper-libs	Medium	Medium	Moderate
CVE-2017-5504	3055	jasper-libs	Medium	Medium	Moderate
CVE-2017-5503	3055	jasper-libs	Medium	Medium	Moderate
CVE-2005-2541	7181	tar	Medium	Medium	Moderate	Ignorable
GHSA-vp35-85q5-9f25	873	github.com/docker/docker	Low	Low
GHSA-c9cp-9c75-9v8c	322	github.com/containerd/containerd	Low	Low
GHSA-77vh-xpmg-72qh	1230	github.com/opencontainers/image-spec	Low	Low
GHSA-5j5w-g665-5m35	1230	github.com/containerd/containerd	Low	Low
CVE-2025-27113	43	libxml2 python3-libxml2	Low	Low	Low
CVE-2025-1632	36	libarchive	Low	Low	Low
CVE-2025-1153	50	gdb-gdbserver	Low	Low	Low
CVE-2025-1152	50	gdb-gdbserver	Low	Low	Low
CVE-2025-1151	50	gdb-gdbserver	Low	Low	Low
CVE-2025-1150	50	gdb-gdbserver	Low	Low	Low
CVE-2025-0725	55	curl libcurl	Low	Low	Low
CVE-2024-57360	71	gdb-gdbserver	Low	Low	Low
CVE-2024-56433	97	shadow-utils	Low	Low	Low
CVE-2024-52006	77	git git-core git-core-doc perl-Git	Low	Low	Low
CVE-2024-51744	148	github.com/golang-jwt/jwt/v4	Low	Low	Low
CVE-2024-50349	77	git git-core git-core-doc perl-Git	Low	Low	Low
CVE-2024-47175	187	cups-libs	Low	High	Important
CVE-2024-43168	238	python3-unbound unbound-libs	Low	Low	Low
CVE-2024-43167	238	python3-unbound unbound-libs	Low	Low	Low
CVE-2024-41996	218	openssl openssl-libs	Low	Low	Low
CVE-2024-34459	329	libxml2 python3-libxml2	Low	Low	Low
CVE-2024-33655	328	python3-unbound unbound-libs	Low	Low	Low
CVE-2024-25260	407	elfutils-debuginfod-client elfutils-default-yama-scope elfutils-libelf elfutils-libs	Low	Low	Low
CVE-2024-13176	71	openssl openssl-libs	Low	Low	Low
CVE-2024-7531	239	nss nss-softokn nss-softokn-freebl nss-sysinit nss-util	Low	Low	Low
CVE-2024-5535	279	openssl openssl-libs	Low	Low	Low
CVE-2024-4741	309	openssl openssl-libs	Low	Low	Low
CVE-2024-4032	289	platform-python python3-libs	Low	Low	Low
CVE-2024-2511	359	openssl openssl-libs	Low	Low	Low
CVE-2024-0727	436	openssl openssl-libs	Low	Low	Low
CVE-2024-0232	538	sqlite-libs	Low	Low	Low
CVE-2023-51257	444	jasper-libs	Low	Low	Low
CVE-2023-50495	477	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2023-45918	432	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2023-45322	588	libxml2 python3-libxml2	Low	Low	Low
CVE-2023-39804	478	tar	Low	Low	Low
CVE-2023-37920	617	ca-certificates	Low	Low	Low
CVE-2023-36191	649	sqlite-libs	Low	Low	Low
CVE-2023-32665	840	glib2	Low	Low	Low
CVE-2023-32636	840	glib2	Low	Low	Low
CVE-2023-32611	840	glib2	Low	Low	Low
CVE-2023-29499	840	glib2	Low	Low	Low
CVE-2023-27534	744	curl libcurl	Low	Low	Low
CVE-2023-25809	735	github.com/opencontainers/runc	Low	Low	Moderate
CVE-2023-24056	802	libpkgconf pkgconf pkgconf-m4 pkgconf-pkg-config	Low	Low	Low
CVE-2023-7216	422	cpio	Low	Low	Low
CVE-2023-2650	673	openssl openssl-libs	Low	Medium	Moderate
CVE-2023-1916	746	libtiff	Low	Low	Low
CVE-2023-0465	736	openssl openssl-libs	Low	Low	Low
CVE-2023-0464	742	openssl openssl-libs	Low	Low	Low
CVE-2022-47011	1019	gdb-gdbserver	Low	Low	Low
CVE-2022-47010	1019	gdb-gdbserver	Low	Low	Low
CVE-2022-47007	1021	gdb-gdbserver	Low	Low	Low
CVE-2022-40755	928	jasper-libs	Low	Low	Low
CVE-2022-27943	1103	libgcc libgomp libstdc++	Low	Low	Low
CVE-2022-3857	880	java-1.8.0-openjdk java-1.8.0-openjdk-devel java-1.8.0-openjdk-headless java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless libpng	Low	Low	Low
CVE-2022-3606	907	libbpf	Low	Low	Low
CVE-2022-3555	898	libX11 libX11-common	Low	Low	Low	Ignorable
CVE-2022-1354	1086	libtiff	Low	Low	Low
CVE-2022-1056	1128	libtiff	Low	Low	Low
CVE-2022-0530	1157	unzip	Low	Low	Low
CVE-2022-0529	1164	unzip	Low	Low	Low
CVE-2021-41089	1276	github.com/docker/docker	Low	Low	Moderate
CVE-2021-39537	1702	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2021-25317	1434	cups-libs	Low	Low	Low
CVE-2021-20193	1536	tar	Low	Medium	Moderate
CVE-2021-4217	1174	unzip	Low	Low	Low
CVE-2021-4209	1197	gnutls	Low	Low	Low
CVE-2021-3997	1178	systemd systemd-libs systemd-pam systemd-udev	Low	Medium	Moderate
CVE-2021-3737	1332	python36	Low	Low	Low
CVE-2020-35538	1731	libjpeg-turbo	Low	Low	Low
CVE-2020-35512	1737	dbus dbus-common dbus-daemon dbus-libs dbus-tools	Low	Low	Low
CVE-2020-21674	1922	libarchive	Low	Medium	Moderate
CVE-2020-19190	2161	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2020-19189	2161	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2020-19188	2161	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2020-19187	2161	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2020-19186	2161	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2020-19185	2161	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2020-18768	2205	libtiff	Low	Low	Low
CVE-2020-12413	1666	nss nss-softokn nss-softokn-freebl nss-sysinit nss-util	Low	Low	Low
CVE-2019-19244	1958	sqlite-libs	Low	Low	Low
CVE-2019-16866	2008	python3-unbound unbound-libs	Low	Low	Low
CVE-2019-14250	2063	libgcc libgomp libstdc++	Low	Low	Low
CVE-2019-13118	2103	libxslt	Low	Low	Low
CVE-2019-13117	2103	libxslt	Low	Low	Low
CVE-2019-9937	2207	sqlite-libs	Low	Low	Low
CVE-2019-9936	2207	sqlite-libs	Low	Low	Low
CVE-2019-9923	2282	tar	Low	Low	Low
CVE-2019-9674	2214	platform-python python3-libs python36	Low	Low	Low
CVE-2019-8906	2281	file file-libs	Low	Low	Low
CVE-2019-7317	2259	libpng	Low	Low	Low
CVE-2018-1000880	2325	libarchive	Low	Low	Low
CVE-2018-1000879	2325	libarchive	Low	Low	Low
CVE-2018-1000654	2425	libtasn1	Low	Low	Low
CVE-2018-20657	2297	libgcc libgomp libstdc++	Low	Low	Low
CVE-2018-20622	2284	jasper-libs	Low	Low	Low
CVE-2018-20570	2287	jasper-libs	Low	Low	Low
CVE-2018-20225	1800	platform-python-pip python3-pip python3-pip-wheel	Low	Low	Low
CVE-2018-19876	2332	cairo cairo-gobject	Low	Low	Low
CVE-2018-19543	2455	jasper-libs	Low	Low	Low
CVE-2018-19542	2455	jasper-libs	Low	Low	Low
CVE-2018-19541	2455	jasper-libs	Low	Low	Low
CVE-2018-19540	2455	jasper-libs	Low	Low	Low
CVE-2018-19539	2455	jasper-libs	Low	Low	Low
CVE-2018-19211	2348	ncurses ncurses-base ncurses-libs	Low	Low	Low
CVE-2018-19210	2348	libtiff	Low	Low	Low
CVE-2018-19139	2336	jasper-libs	Low	Low	Low
CVE-2018-18873	2345	jasper-libs	Low	Low	Low
CVE-2018-17101	2390	libtiff	Low	Low	Low
CVE-2018-10779	2522	libtiff	Low	Low	Low
CVE-2018-5360	2637	libtiff	Low	Low	Low
CVE-2018-1121	2511	procps-ng	Low	Low	Low
CVE-2017-13745	2777	jasper-libs	Low	Low	Low
CVE-2017-9782	2849	jasper-libs	Low	Low	Low
CVE-2017-6519	3655	avahi-libs	Low	Low	Low
CVE-2017-5499	3078	jasper-libs	Low	Low	Low
CVE-2016-20012	3342	openssh openssh-clients	Low	Low	Low	Removable
CVE-2016-4074	3265	jq	Low	Low	Low
CVE-2024-34447	334	bcprov-jdk18on		Medium	Moderate
CVE-2024-29857	292	bcprov-jdk18on		Medium	Moderate
CVE-2024-30172	328	bcprov-jdk18on		Medium	Moderate
CVE-2024-30171	349	bcprov-jdk18on		Medium	Moderate
CVE-2024-28152	392	cloudbees-bitbucket-branch-source		Medium	Moderate
CVE-2024-39460	280	cloudbees-bitbucket-branch-source		Medium	Low
CVE-2024-29133	378	commons-configuration2		Medium	Low
CVE-2024-29131	378	commons-configuration2		Medium	Low
CVE-2021-37533	777	commons-net		Medium	Moderate
CVE-2024-47805	181	credentials		Medium
CVE-2024-11053	112	curl libcurl		Low	Low
CVE-2024-7264	245	curl libcurl		Low	Low
CVE-2022-0235	1174	dnf-plugin-subscription-manager python3-cloud-what python3-subscription-manager-rhsm python3-syspurpose subscription-manager		Medium	Moderate	False Positive
CVE-2023-2004	870	freetype java-11-openjdk java-11-openjdk-devel java-11-openjdk-headless		Negligible		Ignorable
CVE-2023-4156	653	gawk		Low	Low
CVE-2023-2222	842	gdb-gdbserver		Negligible		Ignorable
CVE-2022-41723	774	git-lfs		Medium	Moderate
CVE-2022-41724	777	git-lfs		Medium	Moderate
CVE-2022-41725	777	git-lfs		Medium	Moderate
CVE-2023-24534	729	git-lfs		Medium	Moderate
CVE-2023-24536	729	git-lfs		Medium	Moderate
CVE-2024-24788	329	git-lfs		Medium	Moderate
CVE-2024-9355	183	git-lfs		Medium	Moderate
CVE-2024-34146	335	git-server		Medium	Moderate
GHSA-mq39-4gv4-mvpx	377	github.com/docker/docker		Medium
CVE-2022-3219	930	gnupg2		Low	Low
CVE-2025-30258	14	gnupg2		Low	Low
CVE-2022-41404	903	ini4j		High	Moderate
CVE-2023-51775	398	jose4j		Medium	Moderate
CVE-2024-57699	56	json-smart		High	Important
CVE-2019-12904	2087	libgcrypt		Medium	Moderate
CVE-2024-2236	392	libgcrypt		Medium	Moderate
CVE-2022-4899	990	libzstd		Medium	Moderate
CVE-2021-24032	1511	libzstd		Low	Low
CVE-2019-17543	2086	lz4-libs		Medium	Moderate
CVE-2019-19246	2059	oniguruma		Medium	Moderate
CVE-2025-26465	44	openssh openssh-clients		Medium	Moderate	Removable
CVE-2022-41409	624	pcre2		Low	Low
CVE-2024-39459	280	plain-credentials		Medium	Moderate
CVE-2024-0397	289	platform-python python3-libs python36		Low	Low
CVE-2024-7592	226	platform-python python3-libs python36		Low	Low
CVE-2025-1795	32	platform-python python3-libs python36		Low	Low
CVE-2022-33070	1014	protobuf-c		Low	Low
CVE-2024-52549	139	script-security		Medium	Moderate
CVE-2024-54661	119	socat		Medium	Moderate
CVE-2024-41909	233	sshd-common		High	Moderate
CVE-2022-45047	868	sshd-common		Critical	Important	False Positive
CVE-2023-35887	632	sshd-common		Medium	Moderate
CVE-2023-24531	?	stdlib		Critical
CVE-2023-39323	545	stdlib		High	Moderate
CVE-2023-45285	483	stdlib		High	Moderate
CVE-2024-24787	?	stdlib		Medium
CVE-2024-39458	280	structs		Low	Moderate
CVE-2025-29768	19	vim-minimal		Medium	Moderate
CVE-2018-20786	2291	vim-minimal		Low	Low
CVE-2020-20703	652	vim-minimal		Low	Low
CVE-2021-3236	1539	vim-minimal		Low	Low
CVE-2021-3927	1254	vim-minimal		Low	Low
CVE-2021-3974	1230	vim-minimal		Low	Low
CVE-2021-4166	1194	vim-minimal		Low	Low
CVE-2022-0351	1165	vim-minimal		Low	Low
CVE-2022-1619	1060	vim-minimal		Low	Low
CVE-2022-1720	1055	vim-minimal		Low	Low
CVE-2022-2124	1018	vim-minimal		Low	Low
CVE-2022-2125	1018	vim-minimal		Low	Low
CVE-2022-2126	1018	vim-minimal		Low	Low
CVE-2022-2129	1018	vim-minimal		Low	Low
CVE-2022-2175	1014	vim-minimal		Low	Low
CVE-2022-2182	1014	vim-minimal		Low	Low
CVE-2022-2183	1014	vim-minimal		Low	Low
CVE-2022-2206	1011	vim-minimal		Low	Low
CVE-2022-2207	1010	vim-minimal		Low	Low
CVE-2022-2208	1010	vim-minimal		Low	Low
CVE-2022-2210	1010	vim-minimal		Low	Low
CVE-2022-2284	1005	vim-minimal		Low	Low
CVE-2022-2285	1005	vim-minimal		Low	Low
CVE-2022-2286	1005	vim-minimal		Low	Low
CVE-2022-2287	1004	vim-minimal		Low	Low
CVE-2022-2343	1001	vim-minimal		Low	Low
CVE-2022-2344	1001	vim-minimal		Low	Low
CVE-2022-2345	1002	vim-minimal		Low	Low
CVE-2022-2522	982	vim-minimal		Low	Low
CVE-2022-2819	961	vim-minimal		Low	Low
CVE-2022-2845	959	vim-minimal		Low	Low
CVE-2022-2849	959	vim-minimal		Low	Low
CVE-2022-2923	954	vim-minimal		Low	Low
CVE-2022-2946	953	vim-minimal		Low	Low
CVE-2022-2980	951	vim-minimal		Low	Low
CVE-2022-3037	946	vim-minimal		Low	Low
CVE-2022-3153	937	vim-minimal		Low	Low
CVE-2022-3234	927	vim-minimal		Low	Low
CVE-2022-3235	927	vim-minimal		Low	Low
CVE-2022-3256	923	vim-minimal		Low	Low
CVE-2022-3296	920	vim-minimal		Low	Low
CVE-2022-3352	916	vim-minimal		Low	Low
CVE-2022-3705	889	vim-minimal		Low	Low
CVE-2022-4292	852	vim-minimal		Low	Low
CVE-2022-4293	852	vim-minimal		Low	Low
CVE-2023-0049	819	vim-minimal		Low	Low
CVE-2023-0054	820	vim-minimal		Low	Low
CVE-2023-0288	811	vim-minimal		Low	Low
CVE-2023-0433	802	vim-minimal		Low	Low
CVE-2023-0512	793	vim-minimal		Low	Low
CVE-2023-1127	763	vim-minimal		Low	Low
CVE-2023-1170	760	vim-minimal		Low	Low
CVE-2023-1175	760	vim-minimal		Low	Low
CVE-2023-1264	757	vim-minimal		Low	Low
CVE-2023-2609	694	vim-minimal		Low	Low
CVE-2023-2610	693	vim-minimal		Low	Low
CVE-2023-46246	523	vim-minimal		Low	Low
CVE-2023-4733	576	vim-minimal		Low	Low
CVE-2023-4734	578	vim-minimal		Low	Low
CVE-2023-4735	578	vim-minimal		Low	Low
CVE-2023-4738	578	vim-minimal		Low	Low
CVE-2023-4750	576	vim-minimal		Low	Low
CVE-2023-4751	577	vim-minimal		Low	Low
CVE-2023-4752	576	vim-minimal		Low	Low
CVE-2023-4781	575	vim-minimal		Low	Low
CVE-2023-48231	503	vim-minimal		Low	Low
CVE-2023-48232	503	vim-minimal		Low	Low
CVE-2023-48233	503	vim-minimal		Low	Low
CVE-2023-48234	503	vim-minimal		Low	Low
CVE-2023-48235	503	vim-minimal		Low	Low
CVE-2023-48236	503	vim-minimal		Low	Low
CVE-2023-48237	503	vim-minimal		Low	Low
CVE-2023-48706	497	vim-minimal		Low	Low
CVE-2023-5344	548	vim-minimal		Low	Low
CVE-2023-5441	549	vim-minimal		Low	Low
CVE-2023-5535	540	vim-minimal		Low	Low
CVE-2024-22667	422	vim-minimal		Low	Low
CVE-2024-41965	243	vim-minimal		Low	Low
CVE-2024-43374	229	vim-minimal		Low	Low
CVE-2024-43802	218	vim-minimal		Low	Low
CVE-2024-45306	211	vim-minimal		Low	Low
CVE-2024-47814	176	vim-minimal		Low	Low
CVE-2025-1215	48	vim-minimal		Low	Low
CVE-2025-22134	78	vim-minimal		Low	Low
CVE-2025-24014	71	vim-minimal		Low	Low
CVE-2025-26603	42	vim-minimal		Low	Low
CVE-2024-52550	139	workflow-cps		High	Important

Security Advisory: CVE-2024-45337

Description:

Applications and libraries which misuse connection.serverAuthenticate (via callback field ServerConfig.PublicKeyCallback) may be susceptible to an authorization bypass. The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions. For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key. Since this API is widely misused, as a partial mitigation golang.org/x/cry...@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth. Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

Locations:

/usr/bin/oc
golang.org/x/crypto-v0.0.0-20220331220935-ae2d96664a29

References:

Security Advisory: CVE-2023-28840

Description:

Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby, is commonly referred to as *Docker*.
Swarm Mode, which is compiled in and delivered by default in dockerd and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code.
The overlay network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes.
Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption.
When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. These rules rely on the u32 iptables extension provided by the xt_u32 kernel module to directly filter on a VXLAN packet's VNI field, so that IPSec guarantees can be enforced on encrypted overlay networks without interfering with other overlay networks or other users of VXLAN.
Two iptables rules serve to filter incoming VXLAN datagrams with a VNI that corresponds to an encrypted network and discards unencrypted datagrams. The rules are appended to the end of the INPUT filter chain, following any rules that have been previously set by the system administrator. Administrator-set rules take precedence over the rules Moby sets to discard unencrypted VXLAN datagrams, which can potentially admit unencrypted datagrams that should have been discarded.
The injection of arbitrary Ethernet frames can enable a Denial of Service attack. A sophisticated attacker may be able to establish a UDP or TCP connection by way of the container’s outbound gateway that would otherwise be blocked by a stateful firewall, or carry out other escalations beyond simple injection by smuggling packets into the overlay network.
Patches are available in Moby releases 23.0.3 and 20.10.24. As Mirantis Container Runtime's 20.10 releases are numbered differently, users of that platform should update to 20.10.16.
Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to incoming traffic at the Internet boundary to prevent all VXLAN packet injection, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.

Locations:

/usr/bin/oc
github.com/docker/docker-v20.10.3+incompatible

References:

Security Advisory: GHSA-jq35-85cj-fj4p

Description:

/sys/devices/virtual/powercap accessible by default to containers

Intel's RAPL (Running Average Power Limit) feature, introduced by the Sandy Bridge microarchitecture, provides software insights into hardware energy consumption. To facilitate this, Intel introduced the powercap framework in Linux kernel 3.13, which reads values via relevant MSRs (model specific registers) and provides unprivileged userspace access via sysfs. As RAPL is an interface to access a hardware feature, it is only available when running on bare metal with the module compiled into the kernel.

By 2019, it was realized that in some cases unprivileged access to RAPL readings could be exploited as a power-based side-channel against security features including AES-NI (potentially inside a SGX enclave) and KASLR (kernel address space layout randomization). Also known as the PLATYPUS attack, Intel assigned CVE-2020-8694 and CVE-2020-8695, and AMD assigned CVE-2020-12912.

Several mitigations were applied; Intel reduced the sampling resolution via a microcode update, and the Linux kernel prevents access by non-root users since 5.10. However, this kernel-based mitigation does not apply to many container-based scenarios: * Unless using user namespaces, root inside a container has the same level of privilege as root outside the container, but with a slightly more narrow view of the system * sysfs is mounted inside containers read-only; however only read access is needed to carry out this attack on an unpatched CPU

While this is not a direct vulnerability in container runtimes, defense in depth and safe defaults are valuable and preferred, especially as this poses a risk to multi-tenant container environments running directly on affected hardware. This is provided by masking /sys/devices/virtual/powercap in the default mount configuration, and adding an additional set of rules to deny it in the default AppArmor profile.

While sysfs is not the only way to read from the RAPL subsystem, other ways of accessing it require additional capabilities such as CAP_SYS_RAWIO which is not available to containers by default, or perf paranoia level less than 1, which is a non-default kernel tunable.

References

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8694
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8695
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12912
https://platypusattack.com/
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=949dd0104c496fa7c14991a23c03c62e44637e71
https://web.eece.maine.edu/~vweaver/projects/rapl/

Locations:

/usr/bin/oc
github.com/docker/docker-v20.10.3+incompatible

References:

Security Advisory: GHSA-7ww5-4wqc-m92c

Description:

containerd allows RAPL to be accessible to a container

/sys/devices/virtual/powercap accessible by default to containers

While this is not a direct vulnerability in container runtimes, defense in depth and safe defaults are valuable and preferred, especially as this poses a risk to multi-tenant container environments. This is provided by masking /sys/devices/virtual/powercap in the default mount configuration, and adding an additional set of rules to deny it in the default AppArmor profile.

References

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8694
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8695
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-12912
https://platypusattack.com/
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=949dd0104c496fa7c14991a23c03c62e44637e71
https://web.eece.maine.edu/~vweaver/projects/rapl/

Locations:

/usr/bin/oc
github.com/containerd/containerd-v1.5.1

References:

Security Advisory: CVE-2024-45310

Description:

runc is a CLI tool for spawning and running containers according to the OCI specification. runc 1.1.13 and earlier, as well as 1.2.0-rc2 and earlier, can be tricked into creating empty files or directories in arbitrary locations in the host filesystem by sharing a volume between two containers and exploiting a race with `os.MkdirAll`. While this could be used to create empty files, existing files would not be truncated. An attacker must have the ability to start containers using some kind of custom volume configuration. Containers using user namespaces are still affected, but the scope of places an attacker can create inodes can be significantly reduced. Sufficiently strict LSM policies (SELinux/Apparmor) can also in principle block this attack -- we suspect the industry standard SELinux policy may restrict this attack's scope but the exact scope of protection hasn't been analysed. This is exploitable using runc directly as well as through Docker and Kubernetes. The issue is fixed in runc v1.1.14 and v1.2.0-rc3.
Some workarounds are available. Using user namespaces restricts this attack fairly significantly such that the attacker can only create inodes in directories that the remapped root user/group has write access to. Unless the root user is remapped to an actual
user on the host (such as with rootless containers that don't use `/etc/sub[ug]id`), this in practice means that an attacker would only be able to create inodes in world-writable directories. A strict enough SELinux or AppArmor policy could in principle also restrict the scope if a specific label is applied to the runc runtime, though neither the extent to which the standard existing policies block this attack nor what exact policies are needed to sufficiently restrict this attack have been thoroughly tested.

Locations:

/usr/bin/oc
github.com/opencontainers/runc-v1.0.1

References:

Security Advisory: CVE-2024-29018

Description:

Moby is an open source container framework that is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. Moby's networking implementation allows for many networks, each with their own IP address range and gateway, to be defined. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters and thus behaviors. When creating a network, the `--internal` flag is used to designate a network as _internal_. The `internal` attribute in a docker-compose.yml file may also be used to mark a network _internal_, and other API clients may specify the `internal` parameter as well.
When containers with networking are created, they are assigned unique network interfaces and IP addresses. The host serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.
Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.
In addition to configuring the Linux kernel's various networking features to enable container networking, `dockerd` directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery, and resolution of names from an upstream resolver.
When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver. This request is made from the container's network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself.
As a consequence of this design, containers solely attached to an internal network will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved.
Many systems run a local forwarding DNS resolver. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host's configured resolver, as they cannot reach these addresses on the host loopback device. To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, `dockerd` detects this scenario and instead forward DNS requests from the host namework namespace. The loopback resolver then forwards the requests to its configured upstream resolvers, as expected.
Because `dockerd` forwards DNS requests to the host loopback device, bypassing the container network namespace's normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver. By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers.
Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address.
Moby releases 26.0.0, 25.0.4, and 23.0.11 are patched to prevent forwarding any DNS requests from internal networks. As a workaround, run containers intended to be solely attached to internal networks with a custom upstream address, which will force all upstream DNS queries to be resolved from the container's network namespace.

Locations:

github.com/docker/docker-v20.10.3+incompatible

References:

Security Advisory: CVE-2023-28842

Description:

Moby) is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby is commonly referred to as *Docker*.
Swarm Mode, which is compiled in and delivered by default in `dockerd` and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code.
The `overlay` network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with the VXLAN metadata, including a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes.
Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption.
When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. These rules rely on the `u32` iptables extension provided by the `xt_u32` kernel module to directly filter on a VXLAN packet's VNI field, so that IPSec guarantees can be enforced on encrypted overlay networks without interfering with other overlay networks or other users of VXLAN.
The `overlay` driver dynamically and lazily defines the kernel configuration for the VXLAN network on each node as containers are attached and detached. Routes and encryption parameters are only defined for destination nodes that participate in the network. The iptables rules that prevent encrypted overlay networks from accepting unencrypted packets are not created until a peer is available with which to communicate.
Encrypted overlay networks silently accept cleartext VXLAN datagrams that are tagged with the VNI of an encrypted overlay network. As a result, it is possible to inject arbitrary Ethernet frames into the encrypted overlay network by encapsulating them in VXLAN datagrams. The implications of this can be quite dire, and GHSA-vwm3-crmr-xfxw should be referenced for a deeper exploration.
Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime's 20.10 releases are numbered differently, users of that platform should update to 20.10.16.
Some workarounds are available. In multi-node clusters, deploy a global ‘pause’ container for each encrypted overlay network, on every node. For a single-node cluster, do not use overlay networks of any sort. Bridge networks provide the same connectivity on a single node and have no multi-node features. The Swarm ingress feature is implemented using an overlay network, but can be disabled by publishing ports in `host` mode instead of `ingress` mode (allowing the use of an external load balancer), and removing the `ingress` network. If encrypted overlay networks are in exclusive use, block UDP port 4789 from traffic that has not been validated by IPSec.

Locations:

/usr/bin/oc
github.com/docker/docker-v20.10.3+incompatible

References:

Security Advisory: CVE-2023-28841

Description:

Moby is an open source container framework developed by Docker Inc. that is distributed as Docker, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (`dockerd`), which is developed as moby/moby is commonly referred to as *Docker*.
Swarm Mode, which is compiled in and delivered by default in `dockerd` and is thus present in most major Moby downstreams, is a simple, built-in container orchestrator that is implemented through a combination of SwarmKit and supporting network code.
The `overlay` network driver is a core feature of Swarm Mode, providing isolated virtual LANs that allow communication between containers and services across the cluster. This driver is an implementation/user of VXLAN, which encapsulates link-layer (Ethernet) frames in UDP datagrams that tag the frame with the VXLAN metadata, including a VXLAN Network ID (VNI) that identifies the originating overlay network. In addition, the overlay network driver supports an optional, off-by-default encrypted mode, which is especially useful when VXLAN packets traverses an untrusted network between nodes.
Encrypted overlay networks function by encapsulating the VXLAN datagrams through the use of the IPsec Encapsulating Security Payload protocol in Transport mode. By deploying IPSec encapsulation, encrypted overlay networks gain the additional properties of source authentication through cryptographic proof, data integrity through check-summing, and confidentiality through encryption.
When setting an endpoint up on an encrypted overlay network, Moby installs three iptables (Linux kernel firewall) rules that enforce both incoming and outgoing IPSec. These rules rely on the `u32` iptables extension provided by the `xt_u32` kernel module to directly filter on a VXLAN packet's VNI field, so that IPSec guarantees can be enforced on encrypted overlay networks without interfering with other overlay networks or other users of VXLAN.
An iptables rule designates outgoing VXLAN datagrams with a VNI that corresponds to an encrypted overlay network for IPsec encapsulation.
Encrypted overlay networks on affected platforms silently transmit unencrypted data. As a result, `overlay` networks may appear to be functional, passing traffic as expected, but without any of the expected confidentiality or data integrity guarantees.
It is possible for an attacker sitting in a trusted position on the network to read all of the application traffic that is moving across the overlay network, resulting in unexpected secrets or user data disclosure. Thus, because many database protocols, internal APIs, etc. are not protected by a second layer of encryption, a user may use Swarm encrypted overlay networks to provide confidentiality, which due to this vulnerability this is no longer guaranteed.
Patches are available in Moby releases 23.0.3, and 20.10.24. As Mirantis Container Runtime's 20.10 releases are numbered differently, users of that platform should update to 20.10.16.
Some workarounds are available. Close the VXLAN port (by default, UDP port 4789) to outgoing traffic at the Internet boundary in order to prevent unintentionally leaking unencrypted traffic over the Internet, and/or ensure that the `xt_u32` kernel module is available on all nodes of the Swarm cluster.

Locations:

/usr/bin/oc
github.com/docker/docker-v20.10.3+incompatible

References:

Security Advisory: GHSA-vp35-85q5-9f25

Description:

Container build can leak any path on the host into the container

Description

Moby is the open source Linux container runtime and set of components used to build a variety of downstream container runtimes, including Docker CE, Mirantis Container Runtime (formerly Docker EE), and Docker Desktop. Moby allows for building container images using a set of build instructions (usually named and referred to as a "Dockerfile"), and a build context, which is not unlike the CWD in which the Dockerfile instructions are executed.

Containers may be built using a variety of tools and build backends available in the Moby ecosystem; in all cases, builds may not include files outside of the build context (such as using absolute or relative-parent paths). This is enforced through both checks in the build backends, and the containerization of the build process itself.

Versions of Git where CVE-2022-39253 is present and exploited by a malicious repository, when used in combination with Moby, are subject to an unexpected inclusion of arbitrary filesystem paths in the build context, without any visible warning to the user.

This issue was originally reported by Wenxiang Qian of Tencent Blade Team, and the root-cause analysis was performed by Cory Snider of Mirantis, with assistance from Bjorn Neergaard of the same. The issue was then reported to the Git project, and Taylor Blau led the process resolving the root issue in Git.

Impact

This vulnerability originates in Git, but can be used to violate assumptions that may have security implications for users of Moby and related components. Users may rely on the fact that a build context ensures that outside files cannot be referenced or incorporated using multiple enforcement mechanisms, or expect a warning if this does not hold true. A maliciously crafted Git repository exploiting CVE-2022-39253 can violate this assumption, and potentially include sensitive files that are subsequently uploaded to a container image repository, or disclosed by code inside the resulting container image.

As this issue cannot be triggered remotely, except by users who already have full control over the daemon through the API, and it requires exploiting a vulnerability in Git by convincing a user to build a maliciously crafted repository, the impact in Moby is considered low.

Patches

Moby 20.10.20, and Mirantis Container Runtime (formerly Docker Enterprise Edition) 20.10.14 will contain mitigations for CVE-2022-39253 when a Git clone is performed by Moby components (on either the daemon or API client side). However, as these mitigations only apply to certain scenarios (build of git+<protocol>://... URL contexts) and cannot protect against a malicious repository already on disk, users should update to a version of Git containing patches for CVE-2022-39253 on all their systems running both API clients and daemons.

Specifically, patches in Moby (including patches incorporated from BuildKit) protect against the following:

docker build with the legacy builder (e.g. DOCKER_BUILDKIT unset or set to 0) of a Git URL context. Note that depending on available API versions and the CLI version, the Git clone operation can take place on either the client or the daemon side. Both must be updated (or have Git updated) to fully protect this build method.
docker build with the BuildKit builder (e.g. DOCKER_BUILDKIT=1) of a Git URL context.
docker buildx build with BUILDKIT_CONTEXT_KEEP_GIT_DIR=1 of a Git URL context.

Patches in BuildKit incorporated into Docker Compose protect against CVE-2022-39253 during Compose-driven builds of Git URL contexts.

Patches in Moby and related projects such as BuildKit, the Docker CLI, and Docker Compose cannot fully protect against CVE-2022-39253, as it may be triggered by a malicious repository already on disk that a unpatched Git client has interacted with (specifically, commands that check out submodules such as git clone --recursive, git submodule update, etc. may have already triggered the Git vulnerability).

Workarounds

While this behavior is unexpected and undesirable, and has resulted in this security advisory, users should keep in mind that building a container entails arbitrary code execution. Users should not build a repository/build context they do not trust, as containerization cannot protect against all possible attacks.

When building with BuildKit (e.g. docker buildx build or docker build with DOCKER_BUILDKIT=1), this issue cannot be exploited unless --build-arg BUILDKIT_CONTEXT_KEEP_GIT_DIR=1 was also passed, as by default BuildKit will discard the .git directory of a Git URL context immediately after cloning and checking out the repository.

For more information

If you have any questions or comments about this advisory:

Open an issue
Email us at security@docker.com

Locations:

/usr/bin/oc
github.com/docker/docker-v20.10.3+incompatible

References:

Security Advisory: GHSA-c9cp-9c75-9v8c

Description:

containerd started with non-empty inheritable Linux process capabilities

Impact

A bug was found in containerd where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve(2). Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted.

This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set.

Patches

This bug has been fixed in containerd 1.5.11 and 1.6.2. Users should update to these versions as soon as possible. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset.

This fix changes containerd behavior such that containers are started with a more typical Linux environment. Refer to capabilities(7) for a description of how capabilities work. Note that permitted file capabilities continue to allow for privileges to be raised up to the container's bounding set and that processes may add capabilities to their own inheritable set up to the container's bounding set per the rules described in the manual page. In all cases the container's bounding set provides an upper bound on the capabilities that can be assumed and provides for the container security sandbox.

Workarounds

The entrypoint of a container can be modified to use a utility like capsh(1) to drop inheritable capabilities prior to the primary process starting.

For more information

If you have any questions or comments about this advisory:

Open an issue
Email us at security@containerd.io if you think you’ve found a security bug

Locations:

/usr/bin/oc
github.com/containerd/containerd-v1.5.1

References:

Security Advisory: GHSA-5j5w-g665-5m35

Description:

Ambiguous OCI manifest parsing

Impact

In the OCI Distribution Specification version 1.0.0 and prior and in the OCI Image Specification version 1.0.1 and prior, manifest and index documents are ambiguous without an accompanying Content-Type HTTP header. Versions of containerd prior to 1.4.12 and 1.5.8 treat the Content-Type header as trusted and deserialize the document according to that header. If the Content-Type header changed between pulls of the same ambiguous document (with the same digest), the document may be interpreted differently, meaning that the digest alone is insufficient to unambiguously identify the content of the image.

Patches

This issue has been fixed in containerd 1.4.12 and 1.5.8. Image pulls for manifests that contain a “manifests” field or indices which contain a “layers” field are rejected.

Workarounds

Ensure you only pull images from trusted sources.

References

https://github.com/opencontainers/distribution-spec/security/advisories/GHSA-mc8v-mgrf-8f4m https://github.com/opencontainers/image-spec/security/advisories/GHSA-77vh-xpmg-72qh

For more information

If you have any questions or comments about this advisory: * Open an issue in containerd * Email us at security@containerd.io

Locations:

/usr/bin/oc
github.com/containerd/containerd-v1.5.1

References:

Security Advisory: CVE-2024-51744

Description:

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in `ParseWithClaims` can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by `ParseWithClaims` return both error codes. If users only check for the `jwt.ErrTokenExpired ` using `error.Is`, they will ignore the embedded `jwt.ErrTokenSignatureInvalid` and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the `v5` branch to the `v4` branch. In this logic, the `ParseWithClaims` function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

Locations:

/usr/bin/oc
github.com/golang-jwt/jwt/v4-v4.2.0

References:

Security Advisory: CVE-2022-41725

Description:

A denial of service is possible from excessive resource consumption in net/http and mime/multipart. Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

Locations:

git-lfs-3.4.1-2.el8_10

References:

Security Advisory: CVE-2023-24536

Description:

Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

Locations:

git-lfs-3.4.1-2.el8_10

References:

Security Advisory: GHSA-mq39-4gv4-mvpx

Description:

Moby's external DNS requests from 'internal' networks could lead to data exfiltration

Moby is an open source container framework originally developed by Docker Inc. as Docker. It is a key component of Docker Engine, Docker Desktop, and other distributions of container tooling or runtimes. As a batteries-included container runtime, Moby comes with a built-in networking implementation that enables communication between containers, and between containers and external resources.

Moby's networking implementation allows for creating and using many networks, each with their own subnet and gateway. This feature is frequently referred to as custom networks, as each network can have a different driver, set of parameters, and thus behaviors. When creating a network, the --internal flag is used to designate a network as internal. The internal attribute in a docker-compose.yml file may also be used to mark a network internal, and other API clients may specify the internal parameter as well.

When containers with networking are created, they are assigned unique network interfaces and IP addresses (typically from a non-routable RFC 1918 subnet). The root network namespace (hereafter referred to as the 'host') serves as a router for non-internal networks, with a gateway IP that provides SNAT/DNAT to/from container IPs.

Containers on an internal network may communicate between each other, but are precluded from communicating with any networks the host has access to (LAN or WAN) as no default route is configured, and firewall rules are set up to drop all outgoing traffic. Communication with the gateway IP address (and thus appropriately configured host services) is possible, and the host may communicate with any container IP directly.

In addition to configuring the Linux kernel's various networking features to enable container networking, dockerd directly provides some services to container networks. Principal among these is serving as a resolver, enabling service discovery (looking up other containers on the network by name), and resolution of names from an upstream resolver.

When a DNS request for a name that does not correspond to a container is received, the request is forwarded to the configured upstream resolver (by default, the host's configured resolver). This request is made from the container network namespace: the level of access and routing of traffic is the same as if the request was made by the container itself.

As a consequence of this design, containers solely attached to internal network(s) will be unable to resolve names using the upstream resolver, as the container itself is unable to communicate with that nameserver. Only the names of containers also attached to the internal network are able to be resolved.

Many systems will run a local forwarding DNS resolver, typically present on a loopback address (127.0.0.0/8), such as systemd-resolved or dnsmasq. Common loopback address examples include 127.0.0.1 or 127.0.0.53. As the host and any containers have separate loopback devices, a consequence of the design described above is that containers are unable to resolve names from the host's configured resolver, as they cannot reach these addresses on the host loopback device.

To bridge this gap, and to allow containers to properly resolve names even when a local forwarding resolver is used on a loopback address, dockerd will detect this scenario and instead forward DNS requests from the host/root network namespace. The loopback resolver will then forward the requests to its configured upstream resolvers, as expected.

Impact

Because dockerd will forward DNS requests to the host loopback device, bypassing the container network namespace's normal routing semantics entirely, internal networks can unexpectedly forward DNS requests to an external nameserver.

By registering a domain for which they control the authoritative nameservers, an attacker could arrange for a compromised container to exfiltrate data by encoding it in DNS queries that will eventually be answered by their nameservers. For example, if the domain evil.example was registered, the authoritative nameserver(s) for that domain could (eventually and indirectly) receive a request for this-is-a-secret.evil.example.

Docker Desktop is not affected, as Docker Desktop always runs an internal resolver on a RFC 1918 address.

Patches

Moby releases 26.0.0-rc3, 25.0.5 (released) and 23.0.11 (to be released) are patched to prevent forwarding DNS requests from internal networks.

Workarounds

Run containers intended to be solely attached to internal networks with a custom upstream address (--dns argument to docker run, or API equivalent), which will force all upstream DNS queries to be resolved from the container network namespace.

Background

yair zak originally reported this issue to the Docker security team.
PR https://github.com/moby/moby/pull/46609 was opened in public to fix this issue, as it was not originally considered to have a security implication.
The official documentation claims that "the --internal flag that will completely isolate containers on a network from any communications external to that network," which necessitated this advisory and CVE.

Locations:

/usr/bin/oc