Vulnerabilities |
233 via 647 paths |
|---|---|
Dependencies |
163 |
Source |
Docker |
Target OS |
ubuntu:20.04 |
high severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.40.0-1build1
- Fixed in: 1.40.0-1ubuntu0.2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › nghttp2/libnghttp2-14@1.40.0-1build1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
Remediation
Upgrade Ubuntu:20.04 nghttp2 to version 1.40.0-1ubuntu0.2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-44487
- https://chaos.social/@icing/111210915918780532
- https://github.com/hyperium/hyper/issues/3337
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://www.vicarius.io/vsociety/posts/rapid-reset-cve-2023-44487-dos-in-http2-understanding-the-root-cause
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- http://www.openwall.com/lists/oss-security/2023/10/10/6
- http://www.openwall.com/lists/oss-security/2023/10/10/7
- https://github.com/grpc/grpc/releases/tag/v1.59.2
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2MBEPPC36UBVOZZNAXFHKLFGSLCMN5LI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3N4NJ7FR4X4FPZUGNTQAPSTVB2HB2Y4A/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BFQD3KUEMFBHPAPBGLWQC34L4OWL5HAZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CLB4TW7KALB3EEQWNWCN7OUIWWVWWCG2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/E72T67UPDRXHIDLO3OROR25YAMN4GGW5/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FNA62Q767CFAFHBCDKYNPBMZWB7TWYVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HT7T2R4MQKLIF4ODV4BDLPARWFPCJ5CZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JIZSEFC3YKCGABA2BZW6ZJRMDZJMB7PJ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JMEXY22BFG5Q64HQCM5CK2Q7KDKVV4TY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KSEGD2IWKNUO3DWY4KQGUQM5BISRWHQE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKYHSZQFDNR7RSA7LHVLLIAQMVYCUGBG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LNMZJCDHGLJJLXO4OXWJMTVQRNWOC7UL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VHUHTSXLXGXS7JYKBXTA3VINUPHTNGVU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VSRDIV77HNKUSM7SJC5BKE5JSHLHU2NK/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WE2I52RHNNU42PX6NZ2RBUHSFFJ2LVZX/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WLPRQ5TWUQQXYWBJM7ECYDAIL2YVKIUH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X6QXN4ORIVF6XBW4WWFE7VNPVC74S45Y/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/XFOIBB4YFICHDM7IBOP7PWXW3FX4HLL2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZB43REMKRQR62NJEI7I5NQ4FSXNLBKRT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZKQSIKIAT5TJ3WSLU3RDBQ35YX4GY4V3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ZLU6U2R2IC2K64NDPNMV55AUAO65MAF4/
- https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-http2-reset-d8Kf32vZ
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-44487
- http://www.openwall.com/lists/oss-security/2023/10/13/4
- http://www.openwall.com/lists/oss-security/2023/10/13/9
- http://www.openwall.com/lists/oss-security/2023/10/18/4
- http://www.openwall.com/lists/oss-security/2023/10/18/8
- http://www.openwall.com/lists/oss-security/2023/10/19/6
- http://www.openwall.com/lists/oss-security/2023/10/20/8
- http://www.openwall.com/lists/oss-security/2025/08/13/6
- https://access.redhat.com/security/cve/cve-2023-44487
- https://arstechnica.com/security/2023/10/how-ddosers-used-the-http-2-protocol-to-deliver-attacks-of-unprecedented-size/
- https://aws.amazon.com/security/security-bulletins/AWS-2023-011/
- https://blog.cloudflare.com/technical-breakdown-http2-rapid-reset-ddos-attack/
- https://blog.cloudflare.com/zero-day-rapid-reset-http2-record-breaking-ddos-attack/
- https://blog.litespeedtech.com/2023/10/11/rapid-reset-http-2-vulnerablilty/
- https://blog.qualys.com/vulnerabilities-threat-research/2023/10/10/cve-2023-44487-http-2-rapid-reset-attack
- https://blog.vespa.ai/cve-2023-44487/
- https://bugzilla.proxmox.com/show_bug.cgi?id=4988
- https://bugzilla.redhat.com/show_bug.cgi?id=2242803
- https://bugzilla.suse.com/show_bug.cgi?id=1216123
- https://cgit.freebsd.org/ports/commit/?id=c64c329c2c1752f46b73e3e6ce9f4329be6629f9
- https://cloud.google.com/blog/products/identity-security/google-cloud-mitigated-largest-ddos-attack-peaking-above-398-million-rps/
- https://cloud.google.com/blog/products/identity-security/how-it-works-the-novel-http2-rapid-reset-ddos-attack
- https://community.traefik.io/t/is-traefik-vulnerable-to-cve-2023-44487/20125
- https://discuss.hashicorp.com/t/hcsec-2023-32-vault-consul-and-boundary-affected-by-http-2-rapid-reset-denial-of-service-vulnerability-cve-2023-44487/59715
- https://edg.io/lp/blog/resets-leaks-ddos-and-the-tale-of-a-hidden-cve
- https://forums.swift.org/t/swift-nio-http2-security-update-cve-2023-44487-http-2-dos/67764
- https://gist.github.com/adulau/7c2bfb8e9cdbe4b35a5e131c66a0c088
- https://github.com/Azure/AKS/issues/3947
- https://github.com/Kong/kong/discussions/11741
- https://github.com/advisories/GHSA-qppj-fm5r-hxr3
- https://github.com/advisories/GHSA-vx74-f528-fxqg
- https://github.com/advisories/GHSA-xpw8-rcwv-8f8p
- https://github.com/akka/akka-http/issues/4323
- https://github.com/alibaba/tengine/issues/1872
- https://github.com/apache/apisix/issues/10320
- https://github.com/apache/httpd-site/pull/10
- https://github.com/apache/httpd/blob/afcdbeebbff4b0c50ea26cdd16e178c0d1f24152/modules/http2/h2_mplx.c#L1101-L1113
- https://github.com/apache/tomcat/tree/main/java/org/apache/coyote/http2
- https://github.com/apache/trafficserver/pull/10564
- https://github.com/arkrwn/PoC/tree/main/CVE-2023-44487
- https://github.com/bcdannyboy/CVE-2023-44487
- https://github.com/caddyserver/caddy/issues/5877
- https://github.com/caddyserver/caddy/releases/tag/v2.7.5
- https://github.com/dotnet/announcements/issues/277
- https://github.com/dotnet/core/blob/e4613450ea0da7fd2fc6b61dfb2c1c1dec1ce9ec/release-notes/6.0/6.0.23/6.0.23.md?plain=1#L73
- https://github.com/eclipse/jetty.project/issues/10679
- https://github.com/envoyproxy/envoy/pull/30055
- https://github.com/etcd-io/etcd/issues/16740
- https://github.com/facebook/proxygen/pull/466
- https://github.com/golang/go/issues/63417
- https://github.com/grpc/grpc-go/pull/6703
- https://github.com/h2o/h2o/pull/3291
- https://github.com/h2o/h2o/security/advisories/GHSA-2m7v-gc89-fjqf
- https://github.com/haproxy/haproxy/issues/2312
- https://github.com/icing/mod_h2/blob/0a864782af0a942aa2ad4ed960a6b32cd35bcf0a/mod_http2/README.md?plain=1#L239-L244
- https://github.com/junkurihara/rust-rpxy/issues/97
- https://github.com/kazu-yamamoto/http2/commit/f61d41a502bd0f60eb24e1ce14edc7b6df6722a1
- https://github.com/kazu-yamamoto/http2/issues/93
- https://github.com/kubernetes/kubernetes/pull/121120
- https://github.com/line/armeria/pull/5232
- https://github.com/linkerd/website/pull/1695/commits/4b9c6836471bc8270ab48aae6fd2181bc73fd632
- https://github.com/micrictor/http2-rst-stream
- https://github.com/microsoft/CBL-Mariner/pull/6381
- https://github.com/netty/netty/commit/58f75f665aa81a8cbcf6ffa74820042a285c5e61
- https://github.com/nghttp2/nghttp2/pull/1961
- https://github.com/nghttp2/nghttp2/releases/tag/v1.57.0
- https://github.com/ninenines/cowboy/issues/1615
- https://github.com/nodejs/node/pull/50121
- https://github.com/openresty/openresty/issues/930
- https://github.com/opensearch-project/data-prepper/issues/3474
- https://github.com/oqtane/oqtane.framework/discussions/3367
- https://github.com/projectcontour/contour/pull/5826
- https://github.com/tempesta-tech/tempesta/issues/1986
- https://github.com/varnishcache/varnish-cache/issues/3996
- https://groups.google.com/g/golang-announce/c/iNNxDTCjZvo
- https://istio.io/latest/news/security/istio-security-2023-004/
- https://linkerd.io/2023/10/12/linkerd-cve-2023-44487/
- https://lists.apache.org/thread/5py8h42mxfsn8l1wy6o41xwhsjlsd87q
- https://lists.debian.org/debian-lts-announce/2023/10/msg00020.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00023.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00024.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00045.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00047.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00001.html
- https://lists.debian.org/debian-lts-announce/2023/11/msg00012.html
- https://lists.w3.org/Archives/Public/ietf-http-wg/2023OctDec/0025.html
- https://mailman.nginx.org/pipermail/nginx-devel/2023-October/S36Q5HBXR7CAIMPLLPRSSSYR4PCMWILK.html
- https://martinthomson.github.io/h2-stream-limits/draft-thomson-httpbis-h2-stream-limits.html
- https://msrc.microsoft.com/blog/2023/10/microsoft-response-to-distributed-denial-of-service-ddos-attacks-against-http/2/
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-44487
- https://my.f5.com/manage/s/article/K000137106
- https://netty.io/news/2023/10/10/4-1-100-Final.html
- https://news.ycombinator.com/item?id=37830987
- https://news.ycombinator.com/item?id=37830998
- https://news.ycombinator.com/item?id=37831062
- https://news.ycombinator.com/item?id=37837043
- https://openssf.org/blog/2023/10/10/http-2-rapid-reset-vulnerability-highlights-need-for-rapid-response/
- https://seanmonstar.com/post/730794151136935936/hyper-http2-rapid-reset-unaffected
- https://security.gentoo.org/glsa/202311-09
- https://security.netapp.com/advisory/ntap-20231016-0001/
- https://security.netapp.com/advisory/ntap-20240426-0007/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://security.paloaltonetworks.com/CVE-2023-44487
- https://tomcat.apache.org/security-10.html#Fixed_in_Apache_Tomcat_10.1.14
- https://ubuntu.com/security/CVE-2023-44487
- https://www.bleepingcomputer.com/news/security/new-http-2-rapid-reset-zero-day-attack-breaks-ddos-records/
- https://www.cisa.gov/news-events/alerts/2023/10/10/http2-rapid-reset-vulnerability-cve-2023-44487
- https://www.darkreading.com/cloud/internet-wide-zero-day-bug-fuels-largest-ever-ddos-event
- https://www.debian.org/security/2023/dsa-5521
- https://www.debian.org/security/2023/dsa-5522
- https://www.debian.org/security/2023/dsa-5540
- https://www.debian.org/security/2023/dsa-5549
- https://www.debian.org/security/2023/dsa-5558
- https://www.debian.org/security/2023/dsa-5570
- https://www.haproxy.com/blog/haproxy-is-not-affected-by-the-http-2-rapid-reset-attack-cve-2023-44487
- https://www.netlify.com/blog/netlify-successfully-mitigates-cve-2023-44487/
- https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/
- https://www.openwall.com/lists/oss-security/2023/10/10/6
- https://www.phoronix.com/news/HTTP2-Rapid-Reset-Attack
- https://www.theregister.com/2023/10/10/http2_rapid_reset_zeroday/
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/Appsynergy-io/CVE-2023-44487
- https://www.exploit-db.com/exploits/52426
high severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.17
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but the public structure definition for GENERAL_NAME incorrectly specified the type of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an ASN1_STRING.
When CRL checking is enabled (i.e. the application sets the X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass arbitrary pointers to a memcmp call, enabling them to read memory contents or enact a denial of service. In most cases, the attack requires the attacker to provide both the certificate chain and CRL, neither of which need to have a valid signature. If the attacker only controls one of these inputs, the other input must already contain an X.400 address as a CRL distribution point, which is uncommon. As such, this vulnerability is most likely to only affect applications which have implemented their own functionality for retrieving CRLs over a network.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.17 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-0286
- https://ftp.openbsd.org/pub/OpenBSD/LibreSSL/libressl-3.6.2-relnotes.txt
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.2/common/018_x509.patch.sig
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2c6c9d439b484e1ba9830d8454a34fa4f80fdfe9
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2f7530077e0ef79d98718138716bc51ca0cad658
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fd2af07dc083a350c959147097003a14a5e8ac4d
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://security.gentoo.org/glsa/202402-08
- https://www.openssl.org/news/secadv/20230207.txt
high severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.19-3ubuntu2.2
- Fixed in: 2.2.19-3ubuntu2.5+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnupg2/gpgv@2.2.19-3ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Remediation
Upgrade Ubuntu:20.04 gnupg2 to version 2.2.19-3ubuntu2.5+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-68973
- https://github.com/gpg/gnupg/blob/ff30683418695f5d2cc9e6cf8c9418e09378ebe4/g10/armor.c#L1305-L1306
- https://github.com/gpg/gnupg/commit/115d138ba599328005c5321c0ef9f00355838ca9
- https://github.com/gpg/gnupg/compare/gnupg-2.2.50...gnupg-2.2.51
- https://media.ccc.de/v/39c3-to-sign-or-not-to-sign-practical-vulnerabilities-i
- https://news.ycombinator.com/item?id=46403200
- https://www.openwall.com/lists/oss-security/2025/12/28/5
- http://www.openwall.com/lists/oss-security/2025/12/29/11
- https://lists.debian.org/debian-lts-announce/2026/01/msg00008.html
- https://gpg.fail/memcpy
high severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.14+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.14+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-48384
- https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384
- http://seclists.org/fulldisclosure/2025/Sep/60
- https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
- http://www.openwall.com/lists/oss-security/2025/07/08/4
- https://github.com/liamg/CVE-2025-48384
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
- Fixed in: 2.2.9-1ubuntu0.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.3. dtdCopy in xmlparse.c can have an integer overflow for nDefaultAtts on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Remediation
Upgrade Ubuntu:20.04 expat to version 2.2.9-1ubuntu0.7 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
- Fixed in: 2.2.9-1ubuntu0.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.3. nextScaffoldPart in xmlparse.c can have an integer overflow for m_groupSize on 32-bit platforms (where UINT_MAX equals SIZE_MAX).
Remediation
Upgrade Ubuntu:20.04 expat to version 2.2.9-1ubuntu0.7 or higher.
References
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The PKCS#11 feature in ssh-agent in OpenSSH before 9.3p2 has an insufficiently trustworthy search path, leading to remote code execution if an agent is forwarded to an attacker-controlled system. (Code in /usr/lib is not necessarily safe for loading into ssh-agent.) NOTE: this issue exists because of an incomplete fix for CVE-2016-10009.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.8 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-38408
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CEBTJJINE2I3FHAUKKNQWMFGYMLSMWKQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RAXVQS6ZYTULFAK3TEJHRLKZALJS3AOU/
- http://packetstormsecurity.com/files/173661/OpenSSH-Forwarded-SSH-Agent-Remote-Code-Execution.html
- http://www.openwall.com/lists/oss-security/2023/07/20/1
- http://www.openwall.com/lists/oss-security/2023/07/20/2
- http://www.openwall.com/lists/oss-security/2023/09/22/11
- http://www.openwall.com/lists/oss-security/2023/09/22/9
- https://blog.qualys.com/vulnerabilities-threat-research/2023/07/19/cve-2023-38408-remote-code-execution-in-opensshs-forwarded-ssh-agent
- https://github.com/openbsd/src/commit/7bc29a9d5cd697290aa056e94ecee6253d3425f8
- https://github.com/openbsd/src/commit/f03a4faa55c4ce0818324701dadbf91988d7351d
- https://github.com/openbsd/src/commit/f8f5a6b003981bb824329dc987d101977beda7ca
- https://lists.debian.org/debian-lts-announce/2023/08/msg00021.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CEBTJJINE2I3FHAUKKNQWMFGYMLSMWKQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RAXVQS6ZYTULFAK3TEJHRLKZALJS3AOU/
- https://news.ycombinator.com/item?id=36790196
- https://security.gentoo.org/glsa/202307-01
- https://security.netapp.com/advisory/ntap-20230803-0010/
- https://support.apple.com/kb/HT213940
- https://www.openssh.com/security.html
- https://www.openssh.com/txt/release-9.3p2
- https://www.qualys.com/2023/07/19/cve-2023-38408/rce-openssh-forwarded-ssh-agent.txt
- https://www.vicarius.io/vsociety/posts/exploring-opensshs-agent-forwarding-rce-cve-2023-38408
- https://github.com/kali-mx/CVE-2023-38408
medium severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
- Fixed in: 3.31.1-4ubuntu0.7+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
Remediation
Upgrade Ubuntu:20.04 sqlite3 to version 3.31.1-4ubuntu0.7+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-6965
- https://www.sqlite.org/src/info/5508b56fd24016c13981ec280ecdd833007c9d8dd595edb295b984c2b487b5c8
- http://seclists.org/fulldisclosure/2025/Sep/49
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/56
- http://seclists.org/fulldisclosure/2025/Sep/57
- http://seclists.org/fulldisclosure/2025/Sep/58
- http://www.openwall.com/lists/oss-security/2025/09/06/1
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can cause invalid memory reads during GSS message token handling by sending message tokens with invalid length fields.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.6 or higher.
References
medium severity
- Vulnerable module: wget
- Introduced through: wget@1.20.3-1ubuntu2
- Fixed in: 1.20.3-1ubuntu2.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › wget@1.20.3-1ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in which data that was supposed to be in the userinfo subcomponent is misinterpreted to be part of the host subcomponent.
Remediation
Upgrade Ubuntu:20.04 wget to version 1.20.3-1ubuntu2.1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-38428
- https://security.netapp.com/advisory/ntap-20241115-0005/
- https://git.savannah.gnu.org/cgit/wget.git/commit/?id=ed0c7c7e0e8f7298352646b2fd6e06a11e242ace
- https://lists.debian.org/debian-lts-announce/2025/04/msg00029.html
- https://lists.gnu.org/archive/html/bug-wget/2024-06/msg00005.html
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.13
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a .git/ directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. If symbolic link support is disabled in Git (e.g. via git config --global core.symlinks false), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.13 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-32002
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://git-scm.com/docs/git-clone#Documentation/git-clone.txt---recurse-submodulesltpathspecgt
- https://git-scm.com/docs/git-config#Documentation/git-config.txt-coresymlinks
- https://github.com/git/git/commit/97065761333fd62db1912d81b489db938d8c991d
- https://github.com/git/git/security/advisories/GHSA-8h77-4q3w-gfgv
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
- https://github.com/amalmurali47/git_rce
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
RADIUS Protocol under RFC 2865 is susceptible to forgery attacks by a local attacker who can modify any valid Response (Access-Accept, Access-Reject, or Access-Challenge) to any other response using a chosen-prefix collision attack against MD5 Response Authenticator signature.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.8 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-3596
- https://security.netapp.com/advisory/ntap-20240822-0001/
- https://today.ucsd.edu/story/computer-scientists-discover-vulnerabilities-in-a-popular-security-protocol
- https://cert-portal.siemens.com/productcert/html/ssa-723487.html
- https://cert-portal.siemens.com/productcert/html/ssa-794185.html
- http://www.openwall.com/lists/oss-security/2024/07/09/4
- https://datatracker.ietf.org/doc/draft-ietf-radext-deprecating-radius/
- https://datatracker.ietf.org/doc/html/rfc2865
- https://networkradius.com/assets/pdf/radius_and_md5_collisions.pdf
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0014
- https://www.blastradius.fail/
- https://www.kb.cert.org/vuls/id/456537
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in binutils libbfd.c 2.36 relating to the auxiliary symbol data allows attackers to read or write to system memory or cause a denial of service.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.7 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.
Remediation
There is no fixed version for Ubuntu:20.04 git.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.12+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure.
This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.12+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-32988
- https://access.redhat.com/security/cve/CVE-2025-32988
- https://bugzilla.redhat.com/show_bug.cgi?id=2359622
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.12+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A heap-buffer-overflow (off-by-one) flaw was found in the GnuTLS software in the template parsing logic within the certtool utility. When it reads certain settings from a template file, it allows an attacker to cause an out-of-bounds (OOB) NULL pointer write, resulting in memory corruption and a denial-of-service (DoS) that could potentially crash the system.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.12+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-32990
- https://access.redhat.com/security/cve/CVE-2025-32990
- https://bugzilla.redhat.com/show_bug.cgi?id=2359620
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
medium severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.1-2ubuntu0.2
- Fixed in: 2.10.1-2ubuntu0.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › freetype/libfreetype6@2.10.1-2ubuntu0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An out of bounds write exists in FreeType versions 2.13.0 and below (newer versions of FreeType are not vulnerable) when attempting to parse font subglyph structures related to TrueType GX and variable font files. The vulnerable code assigns a signed short value to an unsigned long and then adds a static value causing it to wrap around and allocate too small of a heap buffer. The code then writes up to 6 signed long integers out of bounds relative to this buffer. This may result in arbitrary code execution. This vulnerability may have been exploited in the wild.
Remediation
Upgrade Ubuntu:20.04 freetype to version 2.10.1-2ubuntu0.4 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-27363
- https://www.facebook.com/security/advisories/cve-2025-27363
- http://www.openwall.com/lists/oss-security/2025/03/13/1
- http://www.openwall.com/lists/oss-security/2025/03/13/11
- http://www.openwall.com/lists/oss-security/2025/03/13/12
- http://www.openwall.com/lists/oss-security/2025/03/13/2
- http://www.openwall.com/lists/oss-security/2025/03/13/3
- http://www.openwall.com/lists/oss-security/2025/03/13/8
- http://www.openwall.com/lists/oss-security/2025/03/14/1
- http://www.openwall.com/lists/oss-security/2025/03/14/2
- http://www.openwall.com/lists/oss-security/2025/03/14/3
- http://www.openwall.com/lists/oss-security/2025/03/14/4
- http://www.openwall.com/lists/oss-security/2025/05/06/3
- https://lists.debian.org/debian-lts-announce/2025/03/msg00030.html
- https://source.android.com/docs/security/bulletin/2025-05-01
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-27363
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog
- https://github.com/tin-z/CVE-2025-27363
medium severity
new
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.55, an out-of-bounds read vulnerability exists in the png_set_quantize() API function. When the function is called with no histogram and the number of colors in the palette is more than twice the maximum supported by the user's display, certain palettes will cause the function to enter into an infinite loop that reads past the end of an internal heap-allocated buffer. The images that trigger this vulnerability are valid per the PNG specification. This vulnerability is fixed in 1.6.55.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm2 or higher.
References
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in the libssh library in versions less than 0.11.2. An out-of-bounds read can be triggered in the sftp_handle function due to an incorrect comparison check that permits the function to access memory beyond the valid handle list and to return an invalid pointer, which is used in further processing. This vulnerability allows an authenticated remote attacker to potentially read unintended memory regions, exposing sensitive information or affect service behavior.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-5318
- https://access.redhat.com/security/cve/CVE-2025-5318
- https://bugzilla.redhat.com/show_bug.cgi?id=2369131
- https://www.libssh.org/security/advisories/CVE-2025-5318.txt
- https://access.redhat.com/errata/RHSA-2025:18231
- https://access.redhat.com/errata/RHSA-2025:18275
- https://access.redhat.com/errata/RHSA-2025:18286
- https://access.redhat.com/errata/RHSA-2025:19012
- https://access.redhat.com/errata/RHSA-2025:19098
- https://access.redhat.com/errata/RHSA-2025:19101
- https://access.redhat.com/errata/RHSA-2025:19400
- https://access.redhat.com/errata/RHSA-2025:19401
- https://access.redhat.com/errata/RHSA-2025:19470
- https://access.redhat.com/errata/RHSA-2025:19472
- https://access.redhat.com/errata/RHSA-2025:19295
- https://access.redhat.com/errata/RHSA-2025:19313
- https://access.redhat.com/errata/RHSA-2025:19300
- https://access.redhat.com/errata/RHSA-2025:19807
- https://access.redhat.com/errata/RHSA-2025:20943
- https://access.redhat.com/errata/RHSA-2025:21013
- https://access.redhat.com/errata/RHSA-2025:19864
- https://access.redhat.com/errata/RHSA-2025:21329
- https://access.redhat.com/errata/RHSA-2025:21829
- https://access.redhat.com/errata/RHSA-2025:22275
- https://access.redhat.com/errata/RHSA-2025:23078
- https://access.redhat.com/errata/RHSA-2025:23079
- https://access.redhat.com/errata/RHSA-2025:23080
- https://access.redhat.com/errata/RHSA-2026:0326
- https://access.redhat.com/errata/RHSA-2026:1541
- https://access.redhat.com/errata/RHSA-2026:3461
- https://access.redhat.com/errata/RHSA-2026:3462
medium severity
- Vulnerable module: perl
- Introduced through: perl@5.30.0-9ubuntu0.3, perl/libperl5.30@5.30.0-9ubuntu0.3 and others
- Fixed in: 5.30.0-9ubuntu0.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl@5.30.0-9ubuntu0.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl/libperl5.30@5.30.0-9ubuntu0.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl/perl-base@5.30.0-9ubuntu0.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl/perl-modules-5.30@5.30.0-9ubuntu0.3
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.
Remediation
Upgrade Ubuntu:20.04 perl to version 5.30.0-9ubuntu0.4 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-31484
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/andk/cpanpm/pull/175
- https://lists.debian.org/debian-lts-announce/2024/10/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- https://metacpan.org/dist/CPAN/changes
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function bfd_mach_o_get_synthetic_symtab in match-o.c.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.9 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered Binutils objdump before 2.39.3 allows attackers to cause a denial of service or other unspecified impacts via function compare_symbols.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.5 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in GNU Binutils up to 2.44. It has been rated as critical. Affected by this issue is the function elf_gc_sweep of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 2.45 is able to address this issue. It is recommended to upgrade the affected component.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-5244
- https://sourceware.org/bugzilla/attachment.cgi?id=16010
- https://sourceware.org/bugzilla/show_bug.cgi?id=32858
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d1458933830456e54223d9fc61f0d9b3a19256f5
- https://vuldb.com/?ctiid.310346
- https://vuldb.com/?id.310346
- https://vuldb.com/?submit.584634
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debug_type_samep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-5245
- https://sourceware.org/bugzilla/attachment.cgi?id=16004
- https://sourceware.org/bugzilla/show_bug.cgi?id=32829
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c3458a8b7ee7d39f070c7b2350851cb2110c65a
- https://vuldb.com/?ctiid.310347
- https://vuldb.com/?id.310347
- https://vuldb.com/?submit.584635
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.45. Affected by this vulnerability is the function copy_section of the file binutils/objcopy.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is named 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-7545
- https://sourceware.org/bugzilla/attachment.cgi?id=16117
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944
- https://vuldb.com/?ctiid.316243
- https://vuldb.com/?id.316243
- https://vuldb.com/?submit.614355
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33049#c1
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.45. The affected element is the function elf_swap_shdr in the library bfd/elfcode.h of the component Linker. The manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 9ca499644a21ceb3f946d1c179c38a83be084490. To fix this issue, it is recommended to deploy a patch. The code maintainer replied with "[f]ixed for 2.46".
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11083
- https://sourceware.org/bugzilla/attachment.cgi?id=16353
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=9ca499644a21ceb3f946d1c179c38a83be084490
- https://vuldb.com/?ctiid.326124
- https://vuldb.com/?id.326124
- https://vuldb.com/?submit.661277
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457
- https://sourceware.org/bugzilla/show_bug.cgi?id=33457#c1
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw has been found in GNU Binutils 2.45. Impacted is the function _bfd_elf_parse_eh_frame of the file bfd/elf-eh-frame.c of the component Linker. Executing manipulation can lead to heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. This patch is called ea1a0737c7692737a644af0486b71e4a392cbca8. A patch should be applied to remediate this issue. The code maintainer replied with "[f]ixed for 2.46".
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11082
- https://sourceware.org/bugzilla/attachment.cgi?id=16358
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464
- https://sourceware.org/bugzilla/show_bug.cgi?id=33464#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ea1a0737c7692737a644af0486b71e4a392cbca8
- https://vuldb.com/?ctiid.326123
- https://vuldb.com/?id.326123
- https://vuldb.com/?submit.661276
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in Binutils addr2line before 2.39.3, function parse_module contains multiple out of bound reads which may cause a denial of service or other unspecified impacts.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.5 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Heap buffer overflow vulnerability in binutils readelf before 2.40 via function display_debug_section in file readelf.c.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.8 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Heap buffer overflow vulnerability in binutils readelf before 2.40 via function find_section_in_set in file readelf.c.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.8 or higher.
References
medium severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
- Fixed in: 2.2.9-1ubuntu0.8+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.
Remediation
Upgrade Ubuntu:20.04 expat to version 2.2.9-1ubuntu0.8+esm1 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, a specially crafted .gitmodules file with submodule URLs that are longer than 1024 characters can used to exploit a bug in config.c::git_config_copy_or_rename_section_in_file(). This bug can be used to inject arbitrary configuration into a user's $GIT_DIR/config when attempting to remove the configuration section associated with that submodule. When the attacker injects configuration values which specify executables to run (such as core.pager, core.editor, core.sshCommand, etc.) this can lead to a remote code execution. A fix A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid running git submodule deinit on untrusted repositories or without prior inspection of any submodule sections in $GIT_DIR/config.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-29007
- https://github.com/git/git/blob/9ce9dea4e1c2419cca126d29fa7730baa078a11b/Documentation/RelNotes/2.30.9.txt
- https://github.com/git/git/commit/528290f8c61222433a8cf02fb7cfffa8438432b4
- https://github.com/git/git/security/advisories/GHSA-v48j-4xgg-4844
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://security.gentoo.org/glsa/202312-15
- https://github.com/ethiack/CVE-2023-29007
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.12
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid cloning repositories from untrusted sources.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.12 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-32004
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://git-scm.com/docs/git-clone
- https://github.com/git/git/commit/f4aa8c8bb11dae6e769cd930565173808cbb69c8
- https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.12
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with git clone --no-local to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a .zip file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.12 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-32465
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://git-scm.com/docs/git#_security
- https://git-scm.com/docs/git-clone
- https://github.com/git/git/commit/7b70e9efb18c2cc3f219af399bd384c5801ba1d7
- https://github.com/git/git/security/advisories/GHSA-vm9j-46j9-qvq4
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
medium severity
- Vulnerable module: less
- Introduced through: less@551-1ubuntu0.1
- Fixed in: 551-1ubuntu0.2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › less@551-1ubuntu0.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream less package and not the less package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
close_altfile in filename.c in less before 606 omits shell_quote calls for LESSCLOSE.
Remediation
Upgrade Ubuntu:20.04 less to version 551-1ubuntu0.2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-48624
- https://github.com/gwsw/less/commit/c6ac6de49698be84d264a0c4c0c40bb870b10144
- https://github.com/gwsw/less/compare/v605...v606
- https://greenwoodsoftware.com/less/
- https://lists.debian.org/debian-lts-announce/2024/05/msg00018.html
- https://security.netapp.com/advisory/ntap-20240605-0010/
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.26 to 1.6.53, there is an integer truncation in the libpng simplified write API functions png_write_image_16bit and png_write_image_8bit causes heap buffer over-read when the caller provides a negative row stride (for bottom-up image layouts) or a stride exceeding 65535 bytes. The bug was introduced in libpng 1.6.26 (October 2016) by casts added to silence compiler warnings on 16-bit systems. This vulnerability is fixed in 1.6.54.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm2 or higher.
References
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.6.9-2ubuntu1.2 and libx11/libx11-data@2:1.6.9-2ubuntu1.2
- Fixed in: 2:1.6.9-2ubuntu1.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-6@2:1.6.9-2ubuntu1.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-data@2:1.6.9-2ubuntu1.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in libX11 due to an integer overflow within the XCreateImage() function. This flaw allows a local user to trigger an integer overflow and execute arbitrary code with elevated privileges.
Remediation
Upgrade Ubuntu:20.04 libx11 to version 2:1.6.9-2ubuntu1.6 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-43787
- http://www.openwall.com/lists/oss-security/2024/01/24/9
- https://jfrog.com/blog/xorg-libx11-vulns-cve-2023-43786-cve-2023-43787-part-two/
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
- https://access.redhat.com/security/cve/CVE-2023-43787
- https://bugzilla.redhat.com/show_bug.cgi?id=2242254
- https://lists.debian.org/debian-lts-announce/2023/10/msg00005.html
medium severity
- Vulnerable module: ncurses/libncurses6
- Introduced through: ncurses/libncurses6@6.2-0ubuntu2, ncurses/libncursesw6@6.2-0ubuntu2 and others
- Fixed in: 6.2-0ubuntu2.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncurses6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncursesw6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libtinfo6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-base@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-bin@6.2-0ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
ncurses before 6.4 20230408, when used by a setuid application, allows local users to trigger security-relevant memory corruption via malformed data in a terminfo database file that is found in $HOME/.terminfo or reached via the TERMINFO or TERM environment variable.
Remediation
Upgrade Ubuntu:20.04 ncurses to version 6.2-0ubuntu2.1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-29491
- http://ncurses.scripts.mit.edu/?p=ncurses.git;a=commit;h=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56
- http://ncurses.scripts.mit.edu/?p=ncurses.git%3Ba=commit%3Bh=eb51b1ea1f75a0ec17c9c5937cb28df1e8eeec56
- http://www.openwall.com/lists/oss-security/2023/04/19/10
- http://www.openwall.com/lists/oss-security/2023/04/19/11
- https://lists.debian.org/debian-lts-announce/2023/12/msg00004.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://security.netapp.com/advisory/ntap-20230517-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
- https://www.openwall.com/lists/oss-security/2023/04/12/5
- https://www.openwall.com/lists/oss-security/2023/04/13/4
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.3.1-5ubuntu4.4, pam/libpam-modules-bin@1.3.1-5ubuntu4.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam-modules@1.3.1-5ubuntu4.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam-modules-bin@1.3.1-5ubuntu4.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam-runtime@1.3.1-5ubuntu4.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam0g@1.3.1-5ubuntu4.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in linux-pam. The pam_namespace module may improperly handle user-controlled paths, allowing local users to exploit symlink attacks and race conditions to elevate their privileges to root. This CVE provides a "complete" fix for CVE-2025-6020.
Remediation
There is no fixed version for Ubuntu:20.04 pam.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-8941
- https://access.redhat.com/security/cve/CVE-2025-8941
- https://bugzilla.redhat.com/show_bug.cgi?id=2388220
- https://access.redhat.com/errata/RHSA-2025:14557
- https://access.redhat.com/errata/RHSA-2025:15100
- https://access.redhat.com/errata/RHSA-2025:15104
- https://access.redhat.com/errata/RHSA-2025:15107
- https://access.redhat.com/errata/RHSA-2025:15099
- https://access.redhat.com/errata/RHSA-2025:15101
- https://access.redhat.com/errata/RHSA-2025:15102
- https://access.redhat.com/errata/RHSA-2025:15103
- https://access.redhat.com/errata/RHSA-2025:15105
- https://access.redhat.com/errata/RHSA-2025:15106
- https://access.redhat.com/errata/RHSA-2025:15709
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:16524
- https://access.redhat.com/errata/RHSA-2025:18219
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:21885
medium severity
- Vulnerable module: perl
- Introduced through: perl@5.30.0-9ubuntu0.3, perl/libperl5.30@5.30.0-9ubuntu0.3 and others
- Fixed in: 5.30.0-9ubuntu0.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl@5.30.0-9ubuntu0.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl/libperl5.30@5.30.0-9ubuntu0.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl/perl-base@5.30.0-9ubuntu0.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › perl/perl-modules-5.30@5.30.0-9ubuntu0.3
NVD Description
Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in perl 5.30.0 through 5.38.0. This issue occurs when a crafted regular expression is compiled by perl, which can allow an attacker controlled byte buffer overflow in a heap allocated buffer.
Remediation
Upgrade Ubuntu:20.04 perl to version 5.30.0-9ubuntu0.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-47038
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNEEWAACXQCEEAKSG7XX2D5YDRWLCIZJ/
- https://perldoc.perl.org/perl5382delta#CVE-2023-47038-Write-past-buffer-end-via-illegal-user-defined-Unicode-property
- https://github.com/Perl/perl5/commit/12c313ce49b36160a7ca2e9b07ad5bd92ee4a010
- https://github.com/Perl/perl5/commit/7047915eef37fccd93e7cd985c29fe6be54650b6
- https://github.com/Perl/perl5/commit/ff1f9f59360afeebd6f75ca1502f5c3ebf077da3
- https://github.com/aquasecurity/trivy/discussions/8400
- https://ubuntu.com/security/CVE-2023-47100
- https://www.suse.com/security/cve/CVE-2023-47100.html
- https://access.redhat.com/errata/RHSA-2024:2228
- https://access.redhat.com/errata/RHSA-2024:3128
- https://access.redhat.com/security/cve/CVE-2023-47038
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056746
- https://bugzilla.redhat.com/show_bug.cgi?id=2249523
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UMDZZ4SCEW6FRWZDMXGAKZ35THTAWFG6/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.10
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability, which was classified as problematic, was found in GNU Binutils up to 2.43. This affects the function disassemble_bytes of the file binutils/objdump.c. The manipulation of the argument buf leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. Upgrading to version 2.44 is able to address this issue. The identifier of the patch is baac6c221e9d69335bf41366a1c7d87d8ab2f893. It is recommended to upgrade the affected component.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.10 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-0840
- https://sourceware.org/bugzilla/attachment.cgi?id=15882
- https://sourceware.org/bugzilla/show_bug.cgi?id=32560
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=baac6c221e9d69335bf41366a1c7d87d8ab2f893
- https://vuldb.com/?ctiid.293997
- https://vuldb.com/?id.293997
- https://vuldb.com/?submit.485255
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Heap-based Buffer Overflow in function bfd_getl32 in Binutils objdump 3.37.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.7 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.
Remediation
There is no fixed version for Ubuntu:20.04 expat.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-8176
- https://access.redhat.com/security/cve/CVE-2024-8176
- https://bugzilla.redhat.com/show_bug.cgi?id=2310137
- https://github.com/libexpat/libexpat/issues/893
- http://www.openwall.com/lists/oss-security/2025/03/15/1
- https://blog.hartwork.org/posts/expat-2-7-0-released/
- https://bugzilla.suse.com/show_bug.cgi?id=1239618
- https://github.com/libexpat/libexpat/blob/R_2_7_0/expat/Changes#L40-L52
- https://gitlab.alpinelinux.org/alpine/aports/-/commit/d068c3ff36fc6f4789988a09c69b434db757db53
- https://security-tracker.debian.org/tracker/CVE-2024-8176
- https://ubuntu.com/security/CVE-2024-8176
- https://security.netapp.com/advisory/ntap-20250328-0009/
- https://access.redhat.com/errata/RHSA-2025:3531
- https://access.redhat.com/errata/RHSA-2025:3734
- https://access.redhat.com/errata/RHSA-2025:3913
- https://access.redhat.com/errata/RHSA-2025:4048
- https://access.redhat.com/errata/RHSA-2025:4447
- https://access.redhat.com/errata/RHSA-2025:4446
- https://access.redhat.com/errata/RHSA-2025:4448
- https://access.redhat.com/errata/RHSA-2025:4449
- https://www.kb.cert.org/vuls/id/760160
- https://access.redhat.com/errata/RHSA-2025:7444
- https://access.redhat.com/errata/RHSA-2025:7512
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:13681
- http://seclists.org/fulldisclosure/2025/May/10
- http://seclists.org/fulldisclosure/2025/May/11
- http://seclists.org/fulldisclosure/2025/May/12
- http://seclists.org/fulldisclosure/2025/May/6
- http://seclists.org/fulldisclosure/2025/May/7
- http://seclists.org/fulldisclosure/2025/May/8
- http://www.openwall.com/lists/oss-security/2025/09/24/11
- https://access.redhat.com/errata/RHSA-2025:22033
- https://access.redhat.com/errata/RHSA-2025:22035
- https://access.redhat.com/errata/RHSA-2025:22034
- https://access.redhat.com/errata/RHSA-2025:22607
- https://access.redhat.com/errata/RHSA-2025:22785
- https://access.redhat.com/errata/RHSA-2025:22842
- https://access.redhat.com/errata/RHSA-2025:22871
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
- Fixed in: 2.2.9-1ubuntu0.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.3. xmlparse.c does not reject a negative length for XML_ParseBuffer.
Remediation
Upgrade Ubuntu:20.04 expat to version 2.2.9-1ubuntu0.7 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-45490
- https://github.com/libexpat/libexpat/issues/887
- https://github.com/libexpat/libexpat/pull/890
- https://security.netapp.com/advisory/ntap-20241018-0004/
- http://seclists.org/fulldisclosure/2024/Dec/10
- http://seclists.org/fulldisclosure/2024/Dec/12
- http://seclists.org/fulldisclosure/2024/Dec/6
- http://seclists.org/fulldisclosure/2024/Dec/7
- http://seclists.org/fulldisclosure/2024/Dec/8
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
medium severity
- Vulnerable module: freetype/libfreetype6
- Introduced through: freetype/libfreetype6@2.10.1-2ubuntu0.2
- Fixed in: 2.10.1-2ubuntu0.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › freetype/libfreetype6@2.10.1-2ubuntu0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Remediation
Upgrade Ubuntu:20.04 freetype to version 2.10.1-2ubuntu0.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-2004
- https://access.redhat.com/security/cve/CVE-2023-2004
- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50462
- https://bugzilla.redhat.com/show_bug.cgi?id=2186428
- https://github.com/freetype/freetype/commit/e6fda039ad638866b7a6a5d046f03278ba1b7611
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4AOSGAOPXLBK4A5ZRTVZ4M6QKVLSWMWG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FEJZMAUB4XP44HSHEBDWEKFGA7DUHY42/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KDNGTGQAUZJ6YQDI2AVGYIFFPUMMZLKS/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NGWWGQULJ7QRNP4GY57HE7OO7VMRWMPN/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RJQI63HWZFL6M26Q6UOHKDY6LD2PFC5Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SFZWDF43D73C5KWFF26GIIVZJKEFPS3K/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VRSEIYMPWLVPGTC34N2Q3WAUHGGOWSWP/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/IHHD6KNH4WLUE6JG6HRQZWNAJMHJ32X7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/SLO7BL2MHZYPY6O3OAEAQL3SKYMGGO6M/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ES2CDRHR2Y4WY6DNDIAPYZFXJU3ZBFAV/
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Prior to versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1, by feeding specially crafted input to git apply --reject, a path outside the working tree can be overwritten with partially controlled contents (corresponding to the rejected hunk(s) from the given patch). A fix is available in versions 2.30.9, 2.31.8, 2.32.7, 2.33.8, 2.34.8, 2.35.8, 2.36.6, 2.37.7, 2.38.5, 2.39.3, and 2.40.1. As a workaround, avoid using git apply with --reject when applying patches from an untrusted source. Use git apply --stat to inspect a patch before applying; avoid applying one that create a conflict where a link corresponding to the *.rej file exists.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-25652
- http://www.openwall.com/lists/oss-security/2023/04/25/2
- https://github.com/git/git/commit/18e2b1cfc80990719275d7b08e6e50f3e8cbc902
- https://github.com/git/git/commit/668f2d53613ac8fd373926ebe219f2c29112d93e
- https://github.com/git/git/security/advisories/GHSA-2hvf-7c8p-28fx
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BSXOGVVBJLYX26IAYX6PJSYQB36BREWH/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://security.gentoo.org/glsa/202312-15
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.10
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git, a revision control system, is vulnerable to path traversal prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8. By feeding a crafted input to git apply, a path outside the working tree can be overwritten as the user who is running git apply. A fix has been prepared and will appear in v2.39.2, v2.38.4, v2.37.6, v2.36.5, v2.35.7, v2.34.7, v2.33.7, v2.32.6, v2.31.7, and v2.30.8. As a workaround, use git apply --stat to inspect a patch before applying; avoid applying one that creates a symbolic link and then creates a file beyond the symbolic link.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.10 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.14
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. Git defines a line-based protocol that is used to exchange information between Git and Git credential helpers. Some ecosystems (most notably, .NET and node.js) interpret single Carriage Return characters as newlines, which renders the protections against CVE-2020-5260 incomplete for credential helpers that treat Carriage Returns in this way. This issue has been addressed in commit b01b9b8 which is included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.14 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-52006
- https://github.com/git-ecosystem/git-credential-manager/security/advisories/GHSA-86c2-4x57-wc8g
- https://github.com/git/git/commit/b01b9b81d36759cdcd07305e78765199e1bc2060
- https://github.com/git/git/security/advisories/GHSA-qm7j-c969-7j4q
- https://github.com/git/git/security/advisories/GHSA-r5ph-xg7q-xfrp
- https://lists.debian.org/debian-lts-announce/2025/01/msg00025.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.10
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in GnuTLS. The response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from the response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue may allow a remote attacker to perform a timing side-channel attack in the RSA-PSK key exchange, potentially leading to the leakage of sensitive data. CVE-2024-0553 is designated as an incomplete resolution for CVE-2023-5981.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.10 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-0553
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://lists.debian.org/debian-lts-announce/2024/02/msg00010.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://security.netapp.com/advisory/ntap-20240202-0011/
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:0627
- https://access.redhat.com/errata/RHSA-2024:0796
- https://access.redhat.com/errata/RHSA-2024:1082
- https://access.redhat.com/errata/RHSA-2024:1108
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2024-0553
- https://bugzilla.redhat.com/show_bug.cgi?id=2258412
- https://gitlab.com/gnutls/gnutls/-/issues/1522
- https://lists.gnupg.org/pipermail/gnutls-help/2024-January/004841.html
medium severity
- Vulnerable module: heimdal/libasn1-8-heimdal
- Introduced through: heimdal/libasn1-8-heimdal@7.7.0+dfsg-1ubuntu1.3, heimdal/libgssapi3-heimdal@7.7.0+dfsg-1ubuntu1.3 and others
- Fixed in: 7.7.0+dfsg-1ubuntu1.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libasn1-8-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libgssapi3-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libhcrypto4-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libheimbase1-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libheimntlm0-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libhx509-5-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libkrb5-26-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libroken18-heimdal@7.7.0+dfsg-1ubuntu1.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › heimdal/libwind0-heimdal@7.7.0+dfsg-1ubuntu1.3
NVD Description
Note: Versions mentioned in the description apply only to the upstream heimdal package and not the heimdal package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The fix for CVE-2022-3437 included changing memcmp to be constant time and a workaround for a compiler bug by adding "!= 0" comparisons to the result of memcmp. When these patches were backported to the heimdal-7.7.1 and heimdal-7.8.0 branches (and possibly other branches) a logic inversion sneaked in causing the validation of message integrity codes in gssapi/arcfour to be inverted.
Remediation
Upgrade Ubuntu:20.04 heimdal to version 7.7.0+dfsg-1ubuntu1.4 or higher.
References
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.21.3, an attacker can modify the plaintext Extra Count field of a confidential GSS krb5 wrap token, causing the unwrapped token to appear truncated to the application.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.6 or higher.
References
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
ec_verify in kdc/kdc_preauth_ec.c in the Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.4 and 1.19.x before 1.19.2 allows remote attackers to cause a NULL pointer dereference and daemon crash. This occurs because a return value is not properly managed in a certain situation.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-36222
- https://github.com/krb5/krb5/commit/fc98f520caefff2e5ee9a0026fdf5109944b3562
- https://www.debian.org/security/2021/dsa-4944
- https://github.com/krb5/krb5/releases
- https://web.mit.edu/kerberos/advisories/
- https://www.oracle.com/security-alerts/cpuoct2021.html
- https://security.netapp.com/advisory/ntap-20211022-0003/
- https://security.netapp.com/advisory/ntap-20211104-0007/
medium severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A weakness has been identified in libssh up to 0.11.3. The impacted element is the function sftp_extensions_get_name/sftp_extensions_get_data of the file src/sftp.c of the component SFTP Extension Name Handler. Executing a manipulation of the argument idx can lead to out-of-bounds read. The attack may be performed from remote. Upgrading to version 0.11.4 and 0.12.0 is sufficient to resolve this issue. This patch is called 855a0853ad3abd4a6cd85ce06fce6d8d4c7a0b60. You should upgrade the affected component.
Remediation
There is no fixed version for Ubuntu:20.04 libssh.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-3731
- https://gitlab.com/libssh/libssh-mirror/-/commit/855a0853ad3abd4a6cd85ce06fce6d8d4c7a0b60
- https://vuldb.com/?ctiid.349709
- https://vuldb.com/?id.349709
- https://vuldb.com/?submit.767120
- https://www.libssh.org/files/0.12/libssh-0.12.0.tar.xz
- https://www.libssh.org/security/advisories/libssh-2026-sftp-extensions.txt
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.6.9-2ubuntu1.2 and libx11/libx11-data@2:1.6.9-2ubuntu1.2
- Fixed in: 2:1.6.9-2ubuntu1.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-6@2:1.6.9-2ubuntu1.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-data@2:1.6.9-2ubuntu1.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in libX11. The security flaw occurs because the functions in src/InitExt.c in libX11 do not check that the values provided for the Request, Event, or Error IDs are within the bounds of the arrays that those functions write to, using those IDs as array indexes. They trust that they were called with values provided by an Xserver adhering to the bounds specified in the X11 protocol, as all X servers provided by X.Org do. As the protocol only specifies a single byte for these values, an out-of-bounds value provided by a malicious server (or a malicious proxy-in-the-middle) can only overwrite other portions of the Display structure and not write outside the bounds of the Display structure itself, possibly causing the client to crash with this memory corruption.
Remediation
Upgrade Ubuntu:20.04 libx11 to version 2:1.6.9-2ubuntu1.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-3138
- https://access.redhat.com/security/cve/CVE-2023-3138
- https://gitlab.freedesktop.org/xorg/lib/libx11/-/commit/304a654a0d57bf0f00d8998185f0360332cfa36c
- https://lists.x.org/archives/xorg-announce/2023-June/003406.html
- https://lists.x.org/archives/xorg-announce/2023-June/003407.html
- https://security.netapp.com/advisory/ntap-20231208-0008/
medium severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.40.0-1build1
- Fixed in: 1.40.0-1ubuntu0.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › nghttp2/libnghttp2-14@1.40.0-1build1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In nghttp2 before version 1.41.0, the overly large HTTP/2 SETTINGS frame payload causes denial of service. The proof of concept attack involves a malicious client constructing a SETTINGS frame with a length of 14,400 bytes (2400 individual settings entries) over and over again. The attack causes the CPU to spike at 100%. nghttp2 v1.41.0 fixes this vulnerability. There is a workaround to this vulnerability. Implement nghttp2_on_frame_recv_callback callback, and if received frame is SETTINGS frame and the number of settings entries are large (e.g., > 32), then drop the connection.
Remediation
Upgrade Ubuntu:20.04 nghttp2 to version 1.40.0-1ubuntu0.1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2020-11080
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-q5wr-xfw9-q7xr
- https://www.debian.org/security/2020/dsa-4696
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AAC2AA36OTRHKSVM5OV7TTVB3CZIGEFL/
- https://github.com/nghttp2/nghttp2/commit/336a98feb0d56b9ac54e12736b18785c27f75090
- https://github.com/nghttp2/nghttp2/commit/f8da73bd042f810f34d19f9eae02b46d870af394
- https://www.oracle.com/security-alerts/cpujan2021.html
- https://www.oracle.com/security-alerts/cpujul2020.html
- https://www.oracle.com/security-alerts/cpuoct2020.html
- https://lists.debian.org/debian-lts-announce/2021/10/msg00011.html
- https://www.oracle.com//security-alerts/cpujul2021.html
- http://lists.opensuse.org/opensuse-security-announce/2020-06/msg00024.html
- https://lists.debian.org/debian-lts-announce/2023/10/msg00023.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/4OOYAMJVLLCLXDTHW3V5UXNULZBBK4O6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AAC2AA36OTRHKSVM5OV7TTVB3CZIGEFL/
- https://www.oracle.com/security-alerts/cpuapr2022.html
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.17
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. "CERTIFICATE"), any header data and the payload data. If the function succeeds then the "name_out", "header" and "data" arguments are populated with pointers to buffers containing the relevant decoded data. The caller is responsible for freeing those buffers. It is possible to construct a PEM file that results in 0 bytes of payload data. In this case PEM_read_bio_ex() will return a failure code but will populate the header argument with a pointer to a buffer that has already been freed. If the caller also frees this buffer then a double free will occur. This will most likely lead to a crash. This could be exploited by an attacker who has the ability to supply malicious PEM files for parsing to achieve a denial of service attack.
The functions PEM_read_bio() and PEM_read() are simple wrappers around PEM_read_bio_ex() and therefore these functions are also directly affected.
These functions are also called indirectly by a number of other OpenSSL functions including PEM_X509_INFO_read_bio_ex() and SSL_CTX_use_serverinfo_file() which are also vulnerable. Some OpenSSL internal uses of these functions are not vulnerable because the caller does not free the header argument if PEM_read_bio_ex() returns a failure code. These locations include the PEM_read_bio_TYPE() functions as well as the decoders introduced in OpenSSL 3.0.
The OpenSSL asn1parse command line application is also impacted by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.17 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-4450
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=63bcf189be73a9cc1264059bed6f57974be74a83
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=bbcf509bd046b34cca19c766bbddc31683d0858b
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://security.gentoo.org/glsa/202402-08
- https://www.openssl.org/news/secadv/20230207.txt
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.17
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by end user applications.
The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter BIO onto the front of it to form a BIO chain, and then returns the new head of the BIO chain to the caller. Under certain conditions, for example if a CMS recipient public key is invalid, the new filter BIO is freed and the function returns a NULL result indicating a failure. However, in this case, the BIO chain is not properly cleaned up and the BIO passed by the caller still retains internal pointers to the previously freed filter BIO. If the caller then goes on to call BIO_pop() on the BIO then a use-after-free will occur. This will most likely result in a crash.
This scenario occurs directly in the internal function B64_write_ASN1() which may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on the BIO. This internal function is in turn called by the public API functions PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream, SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.
Other public API functions that may be impacted by this include i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and i2d_PKCS7_bio_stream.
The OpenSSL cms and smime command line applications are similarly affected.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.17 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-0215
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8818064ce3c3c0f1b740a5aaba2a987e75bfbafd
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9816136fe31d92ace4037d5da5257f763aeeb4eb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=c3829dd8825c654652201e16f8a0a0c46ee3f344
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0003
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230427-0007/
- https://security.netapp.com/advisory/ntap-20230427-0009/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://www.openssl.org/news/secadv/20230207.txt
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A timing side-channel in the handling of RSA ClientKeyExchange messages was discovered in GnuTLS. This side-channel can be sufficient to recover the key encrypted in the RSA ciphertext across a network in a Bleichenbacher style attack. To achieve a successful decryption the attacker would need to send a large amount of specially crafted messages to the vulnerable server. By recovering the secret from the ClientKeyExchange message, the attacker would be able to decrypt the application data exchanged over that connection.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.8 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-0361
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UFIA3X4IZ3CW7SRQ2UHNHNPMRIAWF2FI/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/WS4KVDOG6QTALWHC2QE4Y7VPDRMLTRWQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z634YBXAJ5VLDI62IOPBVP5K6YFHAWCY/
- https://access.redhat.com/security/cve/CVE-2023-0361
- https://github.com/tlsfuzzer/tlsfuzzer/pull/679
- https://gitlab.com/gnutls/gnutls/-/issues/1050
- https://lists.debian.org/debian-lts-announce/2023/02/msg00015.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UFIA3X4IZ3CW7SRQ2UHNHNPMRIAWF2FI/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WS4KVDOG6QTALWHC2QE4Y7VPDRMLTRWQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z634YBXAJ5VLDI62IOPBVP5K6YFHAWCY/
- https://security.netapp.com/advisory/ntap-20230324-0005/
- https://security.netapp.com/advisory/ntap-20230725-0005/
medium severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
- Fixed in: 3.31.1-4ubuntu0.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.
Remediation
Upgrade Ubuntu:20.04 sqlite3 to version 3.31.1-4ubuntu0.6 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-7104
- https://lists.debian.org/debian-lts-announce/2024/09/msg00050.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYONA2XSNFMXLAW4IHLFI5UVV3QRNG5K/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D6C2HN4T2S6GYNTAUXLH45LQZHK7QPHP/
- https://security.netapp.com/advisory/ntap-20240112-0008/
- https://sqlite.org/forum/forumpost/5bcbf4571c
- https://sqlite.org/src/info/0e4e7a05c4204b47
- https://vuldb.com/?ctiid.248999
- https://vuldb.com/?id.248999
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An out-of-bounds read flaw was found in the parse_module function in bfd/vms-alpha.c in Binutils.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-25584
- https://access.redhat.com/security/cve/CVE-2023-25584
- https://bugzilla.redhat.com/show_bug.cgi?id=2167467
- https://security.netapp.com/advisory/ntap-20231103-0002/
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=77c225bdeb410cf60da804879ad41622f5f1aa44
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.12
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the objects/ directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's objects/ directory. When cloning a repository over the filesystem (without explicitly specifying the file:// protocol or --no-local), the optimizations for local cloning
will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.12 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-32021
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://github.com/git/git/security/advisories/GHSA-mvxm-9j2h-qjx7
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From 1.6.51 to 1.6.53, there is a heap buffer over-read in the libpng simplified API function png_image_finish_read when processing interlaced 16-bit PNGs with 8-bit output format and non-minimal row stride. This is a regression introduced by the fix for CVE-2025-65018. This vulnerability is fixed in 1.6.54.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-22695
- https://github.com/pnggroup/libpng/commit/218612ddd6b17944e21eda56caf8b4bf7779d1ea
- https://github.com/pnggroup/libpng/commit/e4f7ad4ea2
- https://github.com/pnggroup/libpng/issues/778
- https://github.com/pnggroup/libpng/security/advisories/GHSA-mmq5-27w3-rxpp
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.12
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in OpenSSH when the VerifyHostKeyDNS option is enabled. A machine-in-the-middle attack can be performed by a malicious machine impersonating a legit server. This issue occurs due to how OpenSSH mishandles error codes in specific conditions when verifying the host key. For an attack to be considered successful, the attacker needs to manage to exhaust the client's memory resource first, turning the attack complexity high.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.12 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-26465
- https://access.redhat.com/security/cve/CVE-2025-26465
- https://bugzilla.redhat.com/show_bug.cgi?id=2344780
- https://blog.qualys.com/vulnerabilities-threat-research/2025/02/18/qualys-tru-discovers-two-vulnerabilities-in-openssh-cve-2025-26465-cve-2025-26466
- https://bugzilla.suse.com/show_bug.cgi?id=1237040
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.6/common/008_ssh.patch.sig
- https://lists.debian.org/debian-lts-announce/2025/02/msg00020.html
- https://lists.mindrot.org/pipermail/openssh-unix-announce/2025-February/000161.html
- https://security-tracker.debian.org/tracker/CVE-2025-26465
- https://security.netapp.com/advisory/ntap-20250228-0003/
- https://ubuntu.com/security/CVE-2025-26465
- https://www.openssh.com/releasenotes.html#9.9p2
- https://www.openwall.com/lists/oss-security/2025/02/18/1
- https://www.openwall.com/lists/oss-security/2025/02/18/4
- https://www.theregister.com/2025/02/18/openssh_vulnerabilities_mitm_dos/
- https://www.vicarius.io/vsociety/posts/cve-2025-26465-detect-vulnerable-openssh
- https://www.vicarius.io/vsociety/posts/cve-2025-26465-mitigate-vulnerable-openssh
- https://access.redhat.com/errata/RHSA-2025:3837
- https://access.redhat.com/errata/RHSA-2025:6993
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:16823
- https://access.redhat.com/solutions/7109879
- http://seclists.org/fulldisclosure/2025/May/7
- http://seclists.org/fulldisclosure/2025/May/8
- http://seclists.org/fulldisclosure/2025/Feb/18
- https://seclists.org/oss-sec/2025/q1/144
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.16
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An allocation of resources without limits or throttling vulnerability exists in curl <v7.88.0 based on the "chained" HTTP compression algorithms, meaning that a server response can be compressed multiple times and potentially with differentalgorithms. The number of acceptable "links" in this "decompression chain" wascapped, but the cap was implemented on a per-header basis allowing a maliciousserver to insert a virtually unlimited number of compression steps simply byusing many headers. The use of such a decompression chain could result in a "malloc bomb", making curl end up spending enormous amounts of allocated heap memory, or trying to and returning out of memory errors.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.16 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-23916
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BQKE6TXYDHOTFHLTBZ5X73GTKI7II5KO/
- https://hackerone.com/reports/1826048
- https://lists.debian.org/debian-lts-announce/2023/02/msg00035.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BQKE6TXYDHOTFHLTBZ5X73GTKI7II5KO/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230309-0006/
- https://www.debian.org/security/2023/dsa-5365
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.21
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
This flaw allows a malicious HTTP server to set "super cookies" in curl that are then passed back to more origins than what is otherwise allowed or possible. This allows a site to set cookies that then would get sent to different and unrelated sites and domains.
It could do this by exploiting a mixed case flaw in curl's function that
verifies a given cookie domain against the Public Suffix List (PSL). For
example a cookie could be set with domain=co.UK when the URL used a lower
case hostname curl.co.uk, even though co.uk is listed as a PSL domain.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.21 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-46218
- https://curl.se/docs/CVE-2023-46218.html
- https://hackerone.com/reports/2212193
- https://lists.debian.org/debian-lts-announce/2023/12/msg00015.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3ZX3VW67N4ACRAPMV2QS2LVYGD7H2MVE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UOGXU25FMMT2X6UUITQ7EZZYMJ42YWWD/
- https://security.netapp.com/advisory/ntap-20240125-0007/
- https://www.debian.org/security/2023/dsa-5587
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.23
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
libcurl's ASN1 parser code has the GTime2str() function, used for parsing an
ASN.1 Generalized Time field. If given an syntactically incorrect field, the
parser might end up using -1 for the length of the time fraction, leading to
a strlen() getting performed on a pointer to a heap buffer area that is not
(purposely) null terminated.
This flaw most likely leads to a crash, but can also lead to heap contents getting returned to the application when CURLINFO_CERTINFO is used.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.23 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-7264
- https://curl.se/docs/CVE-2024-7264.html
- https://curl.se/docs/CVE-2024-7264.json
- https://hackerone.com/reports/2629968
- https://github.com/curl/curl/commit/27959ecce75cdb2809c0bdb3286e60e08fadb519
- https://security.netapp.com/advisory/ntap-20240828-0008/
- http://www.openwall.com/lists/oss-security/2024/07/31/1
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.12+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.12+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-6395
- https://access.redhat.com/security/cve/CVE-2025-6395
- https://bugzilla.redhat.com/show_bug.cgi?id=2376755
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) before 1.20.2 and 1.21.x before 1.21.1 frees an uninitialized pointer. A remote authenticated user can trigger a kadmind crash. This occurs because _xdr_kadm5_principal_ent_rec does not validate the relationship between n_key_data and the key_data array count.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.4 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-36054
- https://github.com/krb5/krb5/commit/ef08b09c9459551aabbe7924fb176f1583053cdd
- https://github.com/krb5/krb5/compare/krb5-1.20.1-final...krb5-1.20.2-final
- https://github.com/krb5/krb5/compare/krb5-1.21-final...krb5-1.21.1-final
- https://lists.debian.org/debian-lts-announce/2023/10/msg00031.html
- https://security.netapp.com/advisory/ntap-20230908-0004/
- https://web.mit.edu/kerberos/www/advisories/
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The Key Distribution Center (KDC) in MIT Kerberos 5 (aka krb5) before 1.18.5 and 1.19.x before 1.19.3 has a NULL pointer dereference in kdc/do_tgs_req.c via a FAST inner body that lacks a server field.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-37750
- https://github.com/krb5/krb5/commit/d775c95af7606a51bf79547a94fa52ddd1cb7f49
- https://security.netapp.com/advisory/ntap-20210923-0002/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MFCLW7D46E4VCREKKH453T5DA4XOLHU2/
- https://github.com/krb5/krb5/releases
- https://web.mit.edu/kerberos/advisories/
- https://lists.debian.org/debian-lts-announce/2021/09/msg00019.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MFCLW7D46E4VCREKKH453T5DA4XOLHU2/
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://www.starwindsoftware.com/security/sw-20220817-0004/
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in libssh, where the authentication check of the connecting client can be bypassed in thepki_verify_data_signature function in memory allocation problems. This issue may happen if there is insufficient memory or the memory usage is limited. The problem is caused by the return value rc, which is initialized to SSH_ERROR and later rewritten to save the return value of the function call pki_key_check_hash_compatible. The value of the variable is not changed between this point and the cryptographic verification. Therefore any error between them calls goto error returning SSH_OK.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-2283
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/27PD44ALQTZXX7K6JAM3BXBUHYA6DFFN/
- http://packetstormsecurity.com/files/172861/libssh-0.9.6-0.10.4-pki_verify_data_signature-Authorization-Bypass.html
- http://seclists.org/fulldisclosure/2025/Feb/18
- https://access.redhat.com/security/cve/CVE-2023-2283
- https://bugzilla.redhat.com/show_bug.cgi?id=2189736
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/27PD44ALQTZXX7K6JAM3BXBUHYA6DFFN/
- https://security.gentoo.org/glsa/202312-05
- https://security.netapp.com/advisory/ntap-20240201-0005/
- https://www.libssh.org/security/advisories/CVE-2023-2283.txt
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A NULL pointer dereference was found In libssh during re-keying with algorithm guessing. This issue may allow an authenticated client to cause a denial of service.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-1667
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/27PD44ALQTZXX7K6JAM3BXBUHYA6DFFN/
- http://www.libssh.org/security/advisories/CVE-2023-1667.txt
- https://access.redhat.com/security/cve/CVE-2023-1667
- https://bugzilla.redhat.com/show_bug.cgi?id=2182199
- https://lists.debian.org/debian-lts-announce/2023/05/msg00029.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/27PD44ALQTZXX7K6JAM3BXBUHYA6DFFN/
- https://security.gentoo.org/glsa/202312-05
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In ssh in OpenSSH before 9.6, OS command injection might occur if a user name or host name has shell metacharacters, and this name is referenced by an expansion token in certain situations. For example, an untrusted Git repository can have a submodule with shell metacharacters in a user name or host name.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-51385
- http://www.openwall.com/lists/oss-security/2025/10/07/1
- http://www.openwall.com/lists/oss-security/2025/10/12/1
- http://seclists.org/fulldisclosure/2024/Mar/21
- http://www.openwall.com/lists/oss-security/2023/12/26/4
- https://github.com/openssh/openssh-portable/commit/7ef3787c84b6b524501211b11a26c742f829af1a
- https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html
- https://security.gentoo.org/glsa/202312-17
- https://security.netapp.com/advisory/ntap-20240105-0005/
- https://support.apple.com/kb/HT214084
- https://vin01.github.io/piptagole/ssh/security/openssh/libssh/remote-code-execution/2023/12/20/openssh-proxycommand-libssh-rce.html
- https://www.debian.org/security/2023/dsa-5586
- https://www.openssh.com/txt/release-9.6
- https://www.openwall.com/lists/oss-security/2023/12/18/2
- https://github.com/vin01/poc-proxycommand-vulnerable
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.19
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Processing some specially crafted ASN.1 object identifiers or data containing them may be very slow.
Impact summary: Applications that use OBJ_obj2txt() directly, or use any of the OpenSSL subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS with no message size limit may experience notable to very long delays when processing those messages, which may lead to a Denial of Service.
An OBJECT IDENTIFIER is composed of a series of numbers - sub-identifiers - most of which have no size limit. OBJ_obj2txt() may be used to translate an ASN.1 OBJECT IDENTIFIER given in DER encoding form (using the OpenSSL type ASN1_OBJECT) to its canonical numeric text form, which are the sub-identifiers of the OBJECT IDENTIFIER in decimal form, separated by periods.
When one of the sub-identifiers in the OBJECT IDENTIFIER is very large (these are sizes that are seen as absurdly large, taking up tens or hundreds of KiBs), the translation to a decimal number in text may take a very long time. The time complexity is O(n^2) with 'n' being the size of the sub-identifiers in bytes (*).
With OpenSSL 3.0, support to fetch cryptographic algorithms using names / identifiers in string form was introduced. This includes using OBJECT IDENTIFIERs in canonical numeric text form as identifiers for fetching algorithms.
Such OBJECT IDENTIFIERs may be received through the ASN.1 structure AlgorithmIdentifier, which is commonly used in multiple protocols to specify what cryptographic algorithm should be used to sign or verify, encrypt or decrypt, or digest passed data.
Applications that call OBJ_obj2txt() directly with untrusted data are affected, with any version of OpenSSL. If the use is for the mere purpose of display, the severity is considered low.
In OpenSSL 3.0 and newer, this affects the subsystems OCSP, PKCS7/SMIME, CMS, CMP/CRMF or TS. It also impacts anything that processes X.509 certificates, including simple things like verifying its signature.
The impact on TLS is relatively low, because all versions of OpenSSL have a 100KiB limit on the peer's certificate chain. Additionally, this only impacts clients, or servers that have explicitly enabled client authentication.
In OpenSSL 1.1.1 and 1.0.2, this only affects displaying diverse objects, such as X.509 certificates. This is assumed to not happen in such a way that it would cause a Denial of Service, so these versions are considered not affected by this issue in such a way that it would be cause for concern, and the severity is therefore considered low.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.19 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-2650
- http://www.openwall.com/lists/oss-security/2023/05/30/1
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=423a2bc737a908ad0c77bda470b2b59dc879936b
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=853c5e56ee0b8650c73140816bb8b91d6163422c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9e209944b35cf82368071f160a744b6178f9b098
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=db779b0e10b047f2585615e0b8f2acdf21f8544a
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2023-0009
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230703-0001/
- https://security.netapp.com/advisory/ntap-20231027-0009/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230530.txt
medium severity
- Vulnerable module: wget
- Introduced through: wget@1.20.3-1ubuntu2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › wget@1.20.3-1ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.
Remediation
There is no fixed version for Ubuntu:20.04 wget.
References
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-27535
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1892780
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0010/
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found that the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange differ from response times of ciphertexts with correct PKCS#1 v1.5 padding.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.9 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-5981
- http://www.openwall.com/lists/oss-security/2024/01/19/3
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/7ZEIOLORQ7N6WRPFXZSYDL2MC4LP7VFV/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GNXKVR5YNUEBNHAHM5GSYKBZX4W2HMN2/
- https://lists.debian.org/debian-lts-announce/2023/11/msg00016.html
- https://access.redhat.com/errata/RHSA-2024:0155
- https://access.redhat.com/errata/RHSA-2024:0319
- https://access.redhat.com/errata/RHSA-2024:0399
- https://access.redhat.com/errata/RHSA-2024:0451
- https://access.redhat.com/errata/RHSA-2024:0533
- https://access.redhat.com/errata/RHSA-2024:1383
- https://access.redhat.com/errata/RHSA-2024:2094
- https://access.redhat.com/security/cve/CVE-2023-5981
- https://bugzilla.redhat.com/show_bug.cgi?id=2248445
- https://gnutls.org/security-new.html#GNUTLS-SA-2023-10-23
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-3576
- https://access.redhat.com/security/cve/CVE-2025-3576
- https://bugzilla.redhat.com/show_bug.cgi?id=2359465
- https://lists.debian.org/debian-lts-announce/2025/05/msg00047.html
- https://access.redhat.com/errata/RHSA-2025:8411
- https://access.redhat.com/errata/RHSA-2025:9418
- https://access.redhat.com/errata/RHSA-2025:9430
- https://access.redhat.com/errata/RHSA-2025:11487
- https://web.mit.edu/kerberos/krb5-1.22/krb5-1.22.html
- https://access.redhat.com/errata/RHSA-2025:13664
- https://access.redhat.com/errata/RHSA-2025:13777
- https://access.redhat.com/errata/RHSA-2025:15000
- https://access.redhat.com/errata/RHSA-2025:15002
- https://access.redhat.com/errata/RHSA-2025:15004
- https://access.redhat.com/errata/RHSA-2025:15001
- https://access.redhat.com/errata/RHSA-2025:15003
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.4 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-48795
- https://www.vicarius.io/vsociety/posts/cve-2023-48795-detect-openssh-vulnerabilit
- https://www.vicarius.io/vsociety/posts/cve-2023-48795-mitigate-openssh-vulnerability
- https://lists.debian.org/debian-lts-announce/2025/04/msg00028.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00042.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00032.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3JIMLVBDWOP4FUPXPTB4PGHHIOMGFLQE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3YQLUQWLIHDB5QCXQEX7HXHAWMOKPP5O/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6Y74KVCPEPT4MVU3LHDWCNNOXOE5ZLUR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/APYIXIQOVDCRWLHTGB4VYMAUIAQLKYJ3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C3AFMZ6MH2UHHOPIWT5YLSFV3D2VB3AC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I724O3LSRCPO4WNVIXTZCT4VVRMXMMSG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L5Y6MNNVAPIJSXJERQ6PKZVCIUXSNJK7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- http://packetstormsecurity.com/files/176280/Terrapin-SSH-Connection-Weakening.html
- http://seclists.org/fulldisclosure/2024/Mar/21
- http://www.openwall.com/lists/oss-security/2023/12/18/3
- http://www.openwall.com/lists/oss-security/2023/12/19/5
- http://www.openwall.com/lists/oss-security/2023/12/20/3
- http://www.openwall.com/lists/oss-security/2024/03/06/3
- http://www.openwall.com/lists/oss-security/2024/04/17/8
- https://access.redhat.com/security/cve/cve-2023-48795
- https://arstechnica.com/security/2023/12/hackers-can-break-ssh-channel-integrity-using-novel-data-corruption-attack/
- https://bugs.gentoo.org/920280
- https://bugzilla.redhat.com/show_bug.cgi?id=2254210
- https://bugzilla.suse.com/show_bug.cgi?id=1217950
- https://crates.io/crates/thrussh/versions
- https://filezilla-project.org/versions.php
- https://forum.netgate.com/topic/184941/terrapin-ssh-attack
- https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.10&id=10e09e273f69e149389b3e0e5d44b8c221c2e7f6
- https://github.com/NixOS/nixpkgs/pull/275249
- https://github.com/PowerShell/Win32-OpenSSH/issues/2189
- https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v9.5.0.0p1-Beta
- https://github.com/TeraTermProject/teraterm/commit/7279fbd6ef4d0c8bdd6a90af4ada2899d786eec0
- https://github.com/TeraTermProject/teraterm/releases/tag/v5.1
- https://github.com/advisories/GHSA-45x7-px36-x8w8
- https://github.com/apache/mina-sshd/issues/445
- https://github.com/connectbot/sshlib/commit/5c8b534f6e97db7ac0e0e579331213aa25c173ab
- https://github.com/connectbot/sshlib/compare/2.2.21...2.2.22
- https://github.com/cyd01/KiTTY/issues/520
- https://github.com/drakkan/sftpgo/releases/tag/v2.5.6
- https://github.com/erlang/otp/blob/d1b43dc0f1361d2ad67601169e90a7fc50bb0369/lib/ssh/doc/src/notes.xml#L39-L42
- https://github.com/erlang/otp/releases/tag/OTP-26.2.1
- https://github.com/golang/crypto/commit/9d2ee975ef9fe627bf0a6f01c1f69e8ef1d4f05d
- https://github.com/hierynomus/sshj/issues/916
- https://github.com/janmojzis/tinyssh/issues/81
- https://github.com/jtesta/ssh-audit/commit/8e972c5e94b460379fe0c7d20209c16df81538a5
- https://github.com/libssh2/libssh2/pull/1291
- https://github.com/mkj/dropbear/blob/17657c36cce6df7716d5ff151ec09a665382d5dd/CHANGES#L25
- https://github.com/mscdex/ssh2/commit/97b223f8891b96d6fc054df5ab1d5a1a545da2a3
- https://github.com/mwiede/jsch/compare/jsch-0.2.14...jsch-0.2.15
- https://github.com/mwiede/jsch/issues/457
- https://github.com/mwiede/jsch/pull/461
- https://github.com/net-ssh/net-ssh/blob/2e65064a52d73396bfc3806c9196fc8108f33cd8/CHANGES.txt#L14-L16
- https://github.com/openssh/openssh-portable/commits/master
- https://github.com/paramiko/paramiko/issues/2337
- https://github.com/proftpd/proftpd/blob/0a7ea9b0ba9fcdf368374a226370d08f10397d99/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/d21e7a2e47e9b38f709bec58e3fa711f759ad0e1/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/issues/456
- https://github.com/rapier1/hpn-ssh/releases
- https://github.com/ronf/asyncssh/blob/develop/docs/changes.rst
- https://github.com/ronf/asyncssh/tags
- https://github.com/ssh-mitm/ssh-mitm/issues/165
- https://github.com/warp-tech/russh/releases/tag/v0.40.2
- https://gitlab.com/libssh/libssh-mirror/-/tags
- https://groups.google.com/g/golang-announce/c/-n5WqVC18LQ
- https://groups.google.com/g/golang-announce/c/qA3XtxvMUyg
- https://help.panic.com/releasenotes/transmit5/
- https://jadaptive.com/important-java-ssh-security-update-new-ssh-vulnerability-discovered-cve-2023-48795/
- https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html
- https://lists.debian.org/debian-lts-announce/2024/01/msg00013.html
- https://lists.debian.org/debian-lts-announce/2024/01/msg00014.html
- https://lists.debian.org/debian-lts-announce/2024/04/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/33XHJUB6ROFUOH2OQNENFROTVH6MHSHA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3CAYYW35MUTNO65RVAELICTNZZFMT2XS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3JIMLVBDWOP4FUPXPTB4PGHHIOMGFLQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3YQLUQWLIHDB5QCXQEX7HXHAWMOKPP5O/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6Y74KVCPEPT4MVU3LHDWCNNOXOE5ZLUR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APYIXIQOVDCRWLHTGB4VYMAUIAQLKYJ3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BL5KTLOSLH2KHRN4HCXJPK3JUVLDGEL6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C3AFMZ6MH2UHHOPIWT5YLSFV3D2VB3AC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CHHITS4PUOZAKFIUBQAQZC7JWXMOYE4B/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F7EYCFQCTSGJXWO3ZZ44MGKFC5HA7G3Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HYEDEXIKFKTUJIN43RG4B7T5ZS6MHUSP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/I724O3LSRCPO4WNVIXTZCT4VVRMXMMSG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KEOTKBUPZXHE3F352JBYNTSNRXYLWD6P/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KMZCVGUGJZZVDPCVDA7TEB22VUCNEXDD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L5Y6MNNVAPIJSXJERQ6PKZVCIUXSNJK7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QI3EHAHABFQK7OABNCSF5GMYP6TONTI7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/33XHJUB6ROFUOH2OQNENFROTVH6MHSHA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HYEDEXIKFKTUJIN43RG4B7T5ZS6MHUSP/
- https://matt.ucc.asn.au/dropbear/CHANGES
- https://nest.pijul.com/pijul/thrussh/changes/D6H7OWTTMHHX6BTB3B6MNBOBX2L66CBL4LGSEUSAI2MCRCJDQFRQC
- https://news.ycombinator.com/item?id=38684904
- https://news.ycombinator.com/item?id=38685286
- https://news.ycombinator.com/item?id=38732005
- https://nova.app/releases/#v11.8
- https://oryx-embedded.com/download/#changelog
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0002
- https://roumenpetrov.info/secsh/#news20231220
- https://security-tracker.debian.org/tracker/CVE-2023-48795
- https://security-tracker.debian.org/tracker/source-package/libssh2
- https://security-tracker.debian.org/tracker/source-package/proftpd-dfsg
- https://security-tracker.debian.org/tracker/source-package/trilead-ssh2
- https://security.gentoo.org/glsa/202312-16
- https://security.gentoo.org/glsa/202312-17
- https://security.netapp.com/advisory/ntap-20240105-0004/
- https://support.apple.com/kb/HT214084
- https://thorntech.com/cve-2023-48795-and-sftp-gateway/
- https://twitter.com/TrueSkrillor/status/1736774389725565005
- https://ubuntu.com/security/CVE-2023-48795
- https://winscp.net/eng/docs/history#6.2.2
- https://www.bitvise.com/ssh-client-version-history#933
- https://www.bitvise.com/ssh-server-version-history
- https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
- https://www.crushftp.com/crush10wiki/Wiki.jsp?page=Update
- https://www.debian.org/security/2023/dsa-5586
- https://www.debian.org/security/2023/dsa-5588
- https://www.freebsd.org/security/advisories/FreeBSD-SA-23:19.openssh.asc
- https://www.lancom-systems.de/service-support/allgemeine-sicherheitshinweise#c243508
- https://www.netsarang.com/en/xshell-update-history/
- https://www.openssh.com/openbsd.html
- https://www.openssh.com/txt/release-9.6
- https://www.openwall.com/lists/oss-security/2023/12/18/2
- https://www.openwall.com/lists/oss-security/2023/12/20/3
- https://www.paramiko.org/changelog.html
- https://www.reddit.com/r/sysadmin/comments/18idv52/cve202348795_why_is_this_cve_still_undisclosed/
- https://www.suse.com/c/suse-addresses-the-ssh-v2-protocol-terrapin-attack-aka-cve-2023-48795/
- https://www.terrapin-attack.com
- https://www.theregister.com/2023/12/20/terrapin_attack_ssh
- https://www.vandyke.com/products/securecrt/history.txt
- https://github.com/projectdiscovery/nuclei-templates/blob/main/javascript/cves/2023/CVE-2023-48795.yaml
- https://github.com/TrixSec/CVE-2023-48795
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.10
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the extension negotiation message), and a client and server may consequently end up with a connection for which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80, AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0, Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15, SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3, Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh crate before 0.40.2 for Rust.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.10 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-48795
- https://www.vicarius.io/vsociety/posts/cve-2023-48795-detect-openssh-vulnerabilit
- https://www.vicarius.io/vsociety/posts/cve-2023-48795-mitigate-openssh-vulnerability
- https://lists.debian.org/debian-lts-announce/2025/04/msg00028.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00042.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00032.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3JIMLVBDWOP4FUPXPTB4PGHHIOMGFLQE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3YQLUQWLIHDB5QCXQEX7HXHAWMOKPP5O/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6Y74KVCPEPT4MVU3LHDWCNNOXOE5ZLUR/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/APYIXIQOVDCRWLHTGB4VYMAUIAQLKYJ3/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C3AFMZ6MH2UHHOPIWT5YLSFV3D2VB3AC/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/I724O3LSRCPO4WNVIXTZCT4VVRMXMMSG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/L5Y6MNNVAPIJSXJERQ6PKZVCIUXSNJK7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- http://packetstormsecurity.com/files/176280/Terrapin-SSH-Connection-Weakening.html
- http://seclists.org/fulldisclosure/2024/Mar/21
- http://www.openwall.com/lists/oss-security/2023/12/18/3
- http://www.openwall.com/lists/oss-security/2023/12/19/5
- http://www.openwall.com/lists/oss-security/2023/12/20/3
- http://www.openwall.com/lists/oss-security/2024/03/06/3
- http://www.openwall.com/lists/oss-security/2024/04/17/8
- https://access.redhat.com/security/cve/cve-2023-48795
- https://arstechnica.com/security/2023/12/hackers-can-break-ssh-channel-integrity-using-novel-data-corruption-attack/
- https://bugs.gentoo.org/920280
- https://bugzilla.redhat.com/show_bug.cgi?id=2254210
- https://bugzilla.suse.com/show_bug.cgi?id=1217950
- https://crates.io/crates/thrussh/versions
- https://filezilla-project.org/versions.php
- https://forum.netgate.com/topic/184941/terrapin-ssh-attack
- https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.10&id=10e09e273f69e149389b3e0e5d44b8c221c2e7f6
- https://github.com/NixOS/nixpkgs/pull/275249
- https://github.com/PowerShell/Win32-OpenSSH/issues/2189
- https://github.com/PowerShell/Win32-OpenSSH/releases/tag/v9.5.0.0p1-Beta
- https://github.com/TeraTermProject/teraterm/commit/7279fbd6ef4d0c8bdd6a90af4ada2899d786eec0
- https://github.com/TeraTermProject/teraterm/releases/tag/v5.1
- https://github.com/advisories/GHSA-45x7-px36-x8w8
- https://github.com/apache/mina-sshd/issues/445
- https://github.com/connectbot/sshlib/commit/5c8b534f6e97db7ac0e0e579331213aa25c173ab
- https://github.com/connectbot/sshlib/compare/2.2.21...2.2.22
- https://github.com/cyd01/KiTTY/issues/520
- https://github.com/drakkan/sftpgo/releases/tag/v2.5.6
- https://github.com/erlang/otp/blob/d1b43dc0f1361d2ad67601169e90a7fc50bb0369/lib/ssh/doc/src/notes.xml#L39-L42
- https://github.com/erlang/otp/releases/tag/OTP-26.2.1
- https://github.com/golang/crypto/commit/9d2ee975ef9fe627bf0a6f01c1f69e8ef1d4f05d
- https://github.com/hierynomus/sshj/issues/916
- https://github.com/janmojzis/tinyssh/issues/81
- https://github.com/jtesta/ssh-audit/commit/8e972c5e94b460379fe0c7d20209c16df81538a5
- https://github.com/libssh2/libssh2/pull/1291
- https://github.com/mkj/dropbear/blob/17657c36cce6df7716d5ff151ec09a665382d5dd/CHANGES#L25
- https://github.com/mscdex/ssh2/commit/97b223f8891b96d6fc054df5ab1d5a1a545da2a3
- https://github.com/mwiede/jsch/compare/jsch-0.2.14...jsch-0.2.15
- https://github.com/mwiede/jsch/issues/457
- https://github.com/mwiede/jsch/pull/461
- https://github.com/net-ssh/net-ssh/blob/2e65064a52d73396bfc3806c9196fc8108f33cd8/CHANGES.txt#L14-L16
- https://github.com/openssh/openssh-portable/commits/master
- https://github.com/paramiko/paramiko/issues/2337
- https://github.com/proftpd/proftpd/blob/0a7ea9b0ba9fcdf368374a226370d08f10397d99/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/d21e7a2e47e9b38f709bec58e3fa711f759ad0e1/RELEASE_NOTES
- https://github.com/proftpd/proftpd/blob/master/RELEASE_NOTES
- https://github.com/proftpd/proftpd/issues/456
- https://github.com/rapier1/hpn-ssh/releases
- https://github.com/ronf/asyncssh/blob/develop/docs/changes.rst
- https://github.com/ronf/asyncssh/tags
- https://github.com/ssh-mitm/ssh-mitm/issues/165
- https://github.com/warp-tech/russh/releases/tag/v0.40.2
- https://gitlab.com/libssh/libssh-mirror/-/tags
- https://groups.google.com/g/golang-announce/c/-n5WqVC18LQ
- https://groups.google.com/g/golang-announce/c/qA3XtxvMUyg
- https://help.panic.com/releasenotes/transmit5/
- https://jadaptive.com/important-java-ssh-security-update-new-ssh-vulnerability-discovered-cve-2023-48795/
- https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html
- https://lists.debian.org/debian-lts-announce/2024/01/msg00013.html
- https://lists.debian.org/debian-lts-announce/2024/01/msg00014.html
- https://lists.debian.org/debian-lts-announce/2024/04/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/33XHJUB6ROFUOH2OQNENFROTVH6MHSHA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3CAYYW35MUTNO65RVAELICTNZZFMT2XS/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3JIMLVBDWOP4FUPXPTB4PGHHIOMGFLQE/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3YQLUQWLIHDB5QCXQEX7HXHAWMOKPP5O/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6Y74KVCPEPT4MVU3LHDWCNNOXOE5ZLUR/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APYIXIQOVDCRWLHTGB4VYMAUIAQLKYJ3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BL5KTLOSLH2KHRN4HCXJPK3JUVLDGEL6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C3AFMZ6MH2UHHOPIWT5YLSFV3D2VB3AC/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CHHITS4PUOZAKFIUBQAQZC7JWXMOYE4B/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F7EYCFQCTSGJXWO3ZZ44MGKFC5HA7G3Y/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HYEDEXIKFKTUJIN43RG4B7T5ZS6MHUSP/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/I724O3LSRCPO4WNVIXTZCT4VVRMXMMSG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KEOTKBUPZXHE3F352JBYNTSNRXYLWD6P/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KMZCVGUGJZZVDPCVDA7TEB22VUCNEXDD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L5Y6MNNVAPIJSXJERQ6PKZVCIUXSNJK7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QI3EHAHABFQK7OABNCSF5GMYP6TONTI7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/33XHJUB6ROFUOH2OQNENFROTVH6MHSHA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HYEDEXIKFKTUJIN43RG4B7T5ZS6MHUSP/
- https://matt.ucc.asn.au/dropbear/CHANGES
- https://nest.pijul.com/pijul/thrussh/changes/D6H7OWTTMHHX6BTB3B6MNBOBX2L66CBL4LGSEUSAI2MCRCJDQFRQC
- https://news.ycombinator.com/item?id=38684904
- https://news.ycombinator.com/item?id=38685286
- https://news.ycombinator.com/item?id=38732005
- https://nova.app/releases/#v11.8
- https://oryx-embedded.com/download/#changelog
- https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0002
- https://roumenpetrov.info/secsh/#news20231220
- https://security-tracker.debian.org/tracker/CVE-2023-48795
- https://security-tracker.debian.org/tracker/source-package/libssh2
- https://security-tracker.debian.org/tracker/source-package/proftpd-dfsg
- https://security-tracker.debian.org/tracker/source-package/trilead-ssh2
- https://security.gentoo.org/glsa/202312-16
- https://security.gentoo.org/glsa/202312-17
- https://security.netapp.com/advisory/ntap-20240105-0004/
- https://support.apple.com/kb/HT214084
- https://thorntech.com/cve-2023-48795-and-sftp-gateway/
- https://twitter.com/TrueSkrillor/status/1736774389725565005
- https://ubuntu.com/security/CVE-2023-48795
- https://winscp.net/eng/docs/history#6.2.2
- https://www.bitvise.com/ssh-client-version-history#933
- https://www.bitvise.com/ssh-server-version-history
- https://www.chiark.greenend.org.uk/~sgtatham/putty/changes.html
- https://www.crushftp.com/crush10wiki/Wiki.jsp?page=Update
- https://www.debian.org/security/2023/dsa-5586
- https://www.debian.org/security/2023/dsa-5588
- https://www.freebsd.org/security/advisories/FreeBSD-SA-23:19.openssh.asc
- https://www.lancom-systems.de/service-support/allgemeine-sicherheitshinweise#c243508
- https://www.netsarang.com/en/xshell-update-history/
- https://www.openssh.com/openbsd.html
- https://www.openssh.com/txt/release-9.6
- https://www.openwall.com/lists/oss-security/2023/12/18/2
- https://www.openwall.com/lists/oss-security/2023/12/20/3
- https://www.paramiko.org/changelog.html
- https://www.reddit.com/r/sysadmin/comments/18idv52/cve202348795_why_is_this_cve_still_undisclosed/
- https://www.suse.com/c/suse-addresses-the-ssh-v2-protocol-terrapin-attack-aka-cve-2023-48795/
- https://www.terrapin-attack.com
- https://www.theregister.com/2023/12/20/terrapin_attack_ssh
- https://www.vandyke.com/products/securecrt/history.txt
- https://github.com/projectdiscovery/nuclei-templates/blob/main/javascript/cves/2023/CVE-2023-48795.yaml
- https://github.com/TrixSec/CVE-2023-48795
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.17
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE.
For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.17 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered function make_tempdir, and make_tempname in bucomm.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.8 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered function stab_demangle_v3_arg in stabs.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.8 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered function parse_stab_struct_fields in stabs.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.8 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered function pr_function_type in prdbg.c in Binutils 2.34 thru 2.38, allows attackers to cause a denial of service due to memory leaks.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.8 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Binutils before 2.40 was discovered to contain a memory leak vulnerability var the function find_abstract_instance in dwarf2.c.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.9 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-48065
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d28fbc7197ba0e021a43f873eff90b05dcdcff6a
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GLZXZXFX2ZWTDU2QZUSZG36LZZVTKUVG/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KGSKF4GH7425S6XFDQMWTJGD5U47BAZN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GLZXZXFX2ZWTDU2QZUSZG36LZZVTKUVG/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KGSKF4GH7425S6XFDQMWTJGD5U47BAZN/
- https://security.netapp.com/advisory/ntap-20231006-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=29925
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git%3Bh=d28fbc7197ba0e021a43f873eff90b05dcdcff6a
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.43/2.44 and classified as problematic. Affected by this vulnerability is the function display_info of the file binutils/bucomm.c of the component objdump. The manipulation leads to memory leak. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named ba6ad3a18cb26b79e0e3b84c39f707535bbc344d. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-3198
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716#c0
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=ba6ad3a18cb26b79e0e3b84c39f707535bbc344d
- https://vuldb.com/?ctiid.303151
- https://vuldb.com/?id.303151
- https://vuldb.com/?submit.545773
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32716
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was determined in GNU Binutils 2.45. The affected element is the function elf_x86_64_relocate_section of the file elf64-x86-64.c of the component Linker. This manipulation causes heap-based buffer overflow. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Patch name: 6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0. To fix this issue, it is recommended to deploy a patch.
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11495
- https://sourceware.org/bugzilla/attachment.cgi?id=16393
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502
- https://sourceware.org/bugzilla/show_bug.cgi?id=33502#c3
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0
- https://vuldb.com/?ctiid.327620
- https://vuldb.com/?id.327620
- https://vuldb.com/?submit.668290
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.45. Impacted is the function _bfd_x86_elf_late_size_sections of the file bfd/elfxx-x86.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. The patch is identified as b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a. A patch should be applied to remediate this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11494
- https://sourceware.org/bugzilla/attachment.cgi?id=16389
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499
- https://sourceware.org/bugzilla/show_bug.cgi?id=33499#c2
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a
- https://vuldb.com/?ctiid.327619
- https://vuldb.com/?id.327619
- https://vuldb.com/?submit.668281
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability has been found in GNU Binutils 2.45. This impacts the function bfd_elf_gc_record_vtentry of the file bfd/elflink.c of the component Linker. The manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 047435dd988a3975d40c6626a8f739a0b2e154bc. To fix this issue, it is recommended to deploy a patch.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11412
- https://sourceware.org/bugzilla/attachment.cgi?id=16378
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452#c8
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=047435dd988a3975d40c6626a8f739a0b2e154bc
- https://vuldb.com/?ctiid.327348
- https://vuldb.com/?id.327348
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was determined in GNU Binutils 2.45. Affected by this vulnerability is the function get_link_hash_entry of the file bfd/elflink.c of the component Linker. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.46 addresses this issue. Patch name: aeaaa9af6359c8e394ce9cf24911fec4f4d23703. It is advisable to upgrade the affected component.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11414
- https://sourceware.org/bugzilla/attachment.cgi?id=16361
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=aeaaa9af6359c8e394ce9cf24911fec4f4d23703
- https://vuldb.com/?ctiid.327350
- https://vuldb.com/?id.327350
- https://vuldb.com/?submit.665591
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=33450
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.45. Affected is the function elf_link_add_object_symbols of the file bfd/elflink.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 2.46 is able to address this issue. The patch is identified as 72efdf166aa0ed72ecc69fc2349af6591a7a19c0. Upgrading the affected component is advised.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11413
- https://sourceware.org/bugzilla/attachment.cgi?id=16362
- https://sourceware.org/bugzilla/show_bug.cgi?id=33456#c10
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=72efdf166aa0ed72ecc69fc2349af6591a7a19c0
- https://vuldb.com/?ctiid.327349
- https://vuldb.com/?id.327349
- https://vuldb.com/?submit.665587
- https://www.gnu.org/
- https://vuldb.com/?submit.665590
- https://sourceware.org/bugzilla/show_bug.cgi?id=33452
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A weakness has been identified in GNU Binutils 2.45. The affected element is the function vfinfo of the file ldmisc.c. Executing a manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 16357. It is best practice to apply a patch to resolve this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-11840
- https://sourceware.org/bugzilla/attachment.cgi?id=16351
- https://sourceware.org/bugzilla/attachment.cgi?id=16357
- https://sourceware.org/bugzilla/show_bug.cgi?id=33455
- https://vuldb.com/?ctiid.328775
- https://vuldb.com/?id.328775
- https://vuldb.com/?submit.661281
- https://www.gnu.org/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in Binutils readelf 2.38.50, reachable assertion failure in function display_debug_names allows attackers to cause a denial of service.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.7 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the function load_separate_debug_files at dwarf2.c. The attacker could supply a crafted ELF file and cause a DNS attack.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.9 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-48063
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=75393a2d54bcc40053e5262a3de9d70c5ebfbbfd
- https://security.netapp.com/advisory/ntap-20231006-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=29924
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git%3Bh=75393a2d54bcc40053e5262a3de9d70c5ebfbbfd
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A security flaw has been discovered in GNU Binutils 2.45. Impacted is the function tg_tag_type of the file prdbg.c. Performing a manipulation results in unchecked return value. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in Binutils. The use of an uninitialized field in the struct module *module may lead to application crash and local denial of service.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-25585
- https://access.redhat.com/security/cve/CVE-2023-25585
- https://bugzilla.redhat.com/show_bug.cgi?id=2167498
- https://security.netapp.com/advisory/ntap-20231103-0003/
- https://sourceware.org/bugzilla/show_bug.cgi?id=29892
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=65cf035b8dc1df5d8020e0b1449514a3c42933e7
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in Binutils. The field the_bfd of asymbolstruct is uninitialized in the bfd_mach_o_get_synthetic_symtab function, which may lead to an application crash and local denial of service.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-25588
- https://access.redhat.com/security/cve/CVE-2023-25588
- https://bugzilla.redhat.com/show_bug.cgi?id=2167505
- https://security.netapp.com/advisory/ntap-20231103-0003/
- https://sourceware.org/bugzilla/show_bug.cgi?id=29677
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=d12f8998d2d086f0a6606589e5aedb7147e6f2f1
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.
Remediation
There is no fixed version for Ubuntu:20.04 expat.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.10
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Using a specially-crafted repository, Git prior to versions 2.39.2, 2.38.4, 2.37.6, 2.36.5, 2.35.7, 2.34.7, 2.33.7, 2.32.6, 2.31.7, and 2.30.8 can be tricked into using its local clone optimization even when using a non-local transport. Though Git will abort local clones whose source $GIT_DIR/objects directory contains symbolic links, the objects directory itself may still be a symbolic link. These two may be combined to include arbitrary files based on known paths on the victim's filesystem within the malicious repository's working copy, allowing for data exfiltration in a similar manner as CVE-2022-39253.
A fix has been prepared and will appear in v2.39.2 v2.38.4 v2.37.6 v2.36.5 v2.35.7 v2.34.7 v2.33.7 v2.32.6, v2.31.7 and v2.30.8. If upgrading is impractical, two short-term workarounds are available. Avoid cloning repositories from untrusted sources with --recurse-submodules. Instead, consider cloning repositories without recursively cloning their submodules, and instead run git submodule update at each layer. Before doing so, inspect each new .gitmodules file to ensure that it does not contain suspicious module URLs.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.10 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-22490
- https://github.com/git/git/commit/c867e4fa180bec4750e9b54eb10f459030dbebfd
- https://github.com/git/git/security/advisories/GHSA-3wp6-j8xr-qw85
- https://github.com/git/git/security/advisories/GHSA-gw92-x3fm-3g3q
- https://security.gentoo.org/glsa/202312-15
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.6.9-2ubuntu1.2 and libx11/libx11-data@2:1.6.9-2ubuntu1.2
- Fixed in: 2:1.6.9-2ubuntu1.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-6@2:1.6.9-2ubuntu1.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-data@2:1.6.9-2ubuntu1.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in libX11 due to an infinite loop within the PutSubImage() function. This flaw allows a local user to consume all available system resources and cause a denial of service condition.
Remediation
Upgrade Ubuntu:20.04 libx11 to version 2:1.6.9-2ubuntu1.6 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-43786
- http://www.openwall.com/lists/oss-security/2024/01/24/9
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/63IBRFLQVZSMOAZBZOBKFWJP26ILRAGQ/
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
- https://access.redhat.com/security/cve/CVE-2023-43786
- https://bugzilla.redhat.com/show_bug.cgi?id=2242253
- https://lists.debian.org/debian-lts-announce/2023/10/msg00005.html
medium severity
- Vulnerable module: libx11/libx11-6
- Introduced through: libx11/libx11-6@2:1.6.9-2ubuntu1.2 and libx11/libx11-data@2:1.6.9-2ubuntu1.2
- Fixed in: 2:1.6.9-2ubuntu1.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-6@2:1.6.9-2ubuntu1.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libx11/libx11-data@2:1.6.9-2ubuntu1.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libx11 package and not the libx11 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in libX11 due to a boundary condition within the _XkbReadKeySyms() function. This flaw allows a local user to trigger an out-of-bounds read error and read the contents of memory on the system.
Remediation
Upgrade Ubuntu:20.04 libx11 to version 2:1.6.9-2ubuntu1.6 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-43785
- https://security.netapp.com/advisory/ntap-20231103-0006/
- https://access.redhat.com/errata/RHSA-2024:2145
- https://access.redhat.com/errata/RHSA-2024:2973
- https://access.redhat.com/security/cve/CVE-2023-43785
- https://bugzilla.redhat.com/show_bug.cgi?id=2242252
- https://lists.debian.org/debian-lts-announce/2023/10/msg00004.html
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.3.1-5ubuntu4.4, pam/libpam-modules-bin@1.3.1-5ubuntu4.4 and others
- Fixed in: 1.3.1-5ubuntu4.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam-modules@1.3.1-5ubuntu4.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam-modules-bin@1.3.1-5ubuntu4.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam-runtime@1.3.1-5ubuntu4.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pam/libpam0g@1.3.1-5ubuntu4.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.
Remediation
Upgrade Ubuntu:20.04 pam to version 1.3.1-5ubuntu4.7 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-22365
- http://www.openwall.com/lists/oss-security/2024/01/18/3
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb
- https://github.com/linux-pam/linux-pam/releases/tag/v1.6.0
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
medium severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
- Fixed in: 3.31.1-4ubuntu0.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In SQLite 3.49.0 before 3.49.1, certain argument values to sqlite3_db_config (in the C-language API) can cause a denial of service (application crash). An sz*nBig multiplication is not cast to a 64-bit integer, and consequently some memory allocations may be incorrect.
Remediation
Upgrade Ubuntu:20.04 sqlite3 to version 3.31.1-4ubuntu0.7 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-29088
- https://gist.github.com/ylwango613/d3883fb9f6ba8a78086356779ce88248
- https://github.com/sqlite/sqlite/commit/56d2fd008b108109f489339f5fd55212bb50afd4
- https://sqlite.org/forum/forumpost/48f365daec
- https://sqlite.org/releaselog/3_49_1.html
- https://www.sqlite.org/cves.html
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@245.4-4ubuntu3.19 and systemd/libudev1@245.4-4ubuntu3.19
- Fixed in: 245.4-4ubuntu3.20
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libsystemd0@245.4-4ubuntu3.19
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libudev1@245.4-4ubuntu3.19
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in systemd. This security flaw can cause a local information leak due to systemd-coredump not respecting the fs.suid_dumpable kernel setting.
Remediation
Upgrade Ubuntu:20.04 systemd to version 245.4-4ubuntu3.20 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-4415
- https://security.netapp.com/advisory/ntap-20230216-0010/
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://github.com/systemd/systemd/commit/b7641425659243c09473cd8fb3aef2c0d4a3eb9c
- https://www.openwall.com/lists/oss-security/2022/12/21/3
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@245.4-4ubuntu3.19 and systemd/libudev1@245.4-4ubuntu3.19
- Fixed in: 245.4-4ubuntu3.20
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libsystemd0@245.4-4ubuntu3.19
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libudev1@245.4-4ubuntu3.19
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An off-by-one Error issue was discovered in Systemd in format_timespan() function of time-util.c. An attacker could supply specific values for time and accuracy that leads to buffer overrun in format_timespan(), leading to a Denial of Service.
Remediation
Upgrade Ubuntu:20.04 systemd to version 245.4-4ubuntu3.20 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-3821
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RVBQC2VLSDVQAPJTEMTREXDL4HYLXG2P/
- https://bugzilla.redhat.com/show_bug.cgi?id=2139327
- https://github.com/systemd/systemd/commit/9102c625a673a3246d7e73d8737f3494446bad4e
- https://github.com/systemd/systemd/issues/23928
- https://github.com/systemd/systemd/pull/23933
- https://lists.debian.org/debian-lts-announce/2023/06/msg00036.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RVBQC2VLSDVQAPJTEMTREXDL4HYLXG2P/
- https://security.gentoo.org/glsa/202305-15
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.30+dfsg-7ubuntu0.20.04.2
- Fixed in: 1.30+dfsg-7ubuntu0.20.04.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › tar@1.30+dfsg-7ubuntu0.20.04.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in from_header in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.
Remediation
Upgrade Ubuntu:20.04 tar to version 1.30+dfsg-7ubuntu0.20.04.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-48303
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CRY7VEL4AIG3GLIEVCTOXRZNSVYDYYUD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/X5VQYCO52Z7GAVCLRYUITN7KXHLRZQS4/
- https://savannah.gnu.org/bugs/?62387
- https://savannah.gnu.org/patch/?10307
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.12
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in GnuTLS, which relies on libtasn1 for ASN.1 data processing. Due to an inefficient algorithm in libtasn1, decoding certain DER-encoded certificate data can take excessive time, leading to increased resource consumption. This flaw allows a remote attacker to send a specially crafted certificate, causing GnuTLS to become unresponsive or slow, resulting in a denial-of-service condition.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.12 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-12243
- https://access.redhat.com/security/cve/CVE-2024-12243
- https://bugzilla.redhat.com/show_bug.cgi?id=2344615
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- https://lists.debian.org/debian-lts-announce/2025/02/msg00027.html
- https://access.redhat.com/errata/RHSA-2025:4051
- https://access.redhat.com/errata/RHSA-2025:7076
- https://access.redhat.com/errata/RHSA-2025:8020
- https://security.netapp.com/advisory/ntap-20250523-0002/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17361
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in the libssh implements abstract layer for message digest (MD) operations implemented by different supported crypto backends. The return values from these were not properly checked, which could cause low-memory situations failures, NULL dereferences, crashes, or usage of the uninitialized memory as an input for the KDF. In this case, non-matching keys will result in decryption/integrity failures, terminating the connection.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-6918
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- https://access.redhat.com/errata/RHSA-2024:2504
- https://access.redhat.com/errata/RHSA-2024:3233
- https://access.redhat.com/security/cve/CVE-2023-6918
- https://bugzilla.redhat.com/show_bug.cgi?id=2254997
- https://security.netapp.com/advisory/ntap-20250214-0009/
- https://www.libssh.org/2023/12/18/libssh-0-10-6-and-libssh-0-9-8-security-releases/
- https://www.libssh.org/security/advisories/CVE-2023-6918.txt
medium severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.16.0-2
- Fixed in: 4.16.0-2ubuntu0.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libtasn1-6@4.16.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw in libtasn1 causes inefficient handling of specific certificate data. When processing a large number of elements in a certificate, libtasn1 takes much longer than expected, which can slow down or even crash the system. This flaw allows an attacker to send a specially crafted certificate, causing a denial of service attack.
Remediation
Upgrade Ubuntu:20.04 libtasn1-6 to version 4.16.0-2ubuntu0.1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-12133
- https://access.redhat.com/security/cve/CVE-2024-12133
- https://bugzilla.redhat.com/show_bug.cgi?id=2344611
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- http://www.openwall.com/lists/oss-security/2025/02/06/6
- https://lists.debian.org/debian-lts-announce/2025/02/msg00025.html
- https://access.redhat.com/errata/RHSA-2025:4049
- https://access.redhat.com/errata/RHSA-2025:7077
- https://access.redhat.com/errata/RHSA-2025:8021
- https://security.netapp.com/advisory/ntap-20250523-0003/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17347
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability classified as critical was found in GNU Binutils 2.43. This vulnerability affects the function _bfd_elf_gc_mark_rsec of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 931494c9a89558acb36a03a340c01726545eef24. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-1181
- https://sourceware.org/bugzilla/attachment.cgi?id=15918
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=931494c9a89558acb36a03a340c01726545eef24
- https://vuldb.com/?ctiid.295084
- https://vuldb.com/?id.295084
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250425-0007/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32643
- https://vuldb.com/?submit.495402
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability, which was classified as critical, was found in GNU Binutils 2.43. Affected is the function bfd_elf_reloc_symbol_deleted_p of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as b425859021d17adf62f06fb904797cf8642986ad. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-1182
- https://sourceware.org/bugzilla/attachment.cgi?id=15919
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b425859021d17adf62f06fb904797cf8642986ad
- https://vuldb.com/?ctiid.295086
- https://vuldb.com/?id.295086
- https://www.gnu.org/
- https://sourceware.org/bugzilla/show_bug.cgi?id=32644
- https://vuldb.com/?submit.495407
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in libssh. By utilizing the ProxyCommand or ProxyJump feature, users can exploit unchecked hostname syntax on the client. This issue may allow an attacker to inject malicious code into the command of the features mentioned through the hostname parameter.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-6004
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LZQVUHWVWRH73YBXUQJOD6CKHDQBU3DM/
- https://security.netapp.com/advisory/ntap-20240223-0004/
- https://access.redhat.com/errata/RHSA-2024:2504
- https://access.redhat.com/errata/RHSA-2024:3233
- https://access.redhat.com/security/cve/CVE-2023-6004
- https://bugzilla.redhat.com/show_bug.cgi?id=2251110
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/MKQRBF3DWMWPH36LBCOBUTSIZRTPEZXB/
- https://www.libssh.org/security/advisories/CVE-2023-6004.txt
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.14
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When Git asks for credentials via a terminal prompt (i.e. without using any credential helper), it prints out the host name for which the user is expected to provide a username and/or a password. At this stage, any URL-encoded parts have been decoded already, and are printed verbatim. This allows attackers to craft URLs that contain ANSI escape sequences that the terminal interpret to confuse users e.g. into providing passwords for trusted Git hosting sites when in fact they are then sent to untrusted sites that are under the attacker's control. This issue has been patch via commits 7725b81 and c903985 which are included in release versions v2.48.1, v2.47.2, v2.46.3, v2.45.3, v2.44.3, v2.43.6, v2.42.4, v2.41.3, and v2.40.4. Users are advised to upgrade. Users unable to upgrade should avoid cloning from untrusted URLs, especially recursive clones.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.14 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-50349
- https://github.com/git/git/commit/7725b8100ffbbff2750ee4d61a0fcc1f53a086e8
- https://github.com/git/git/commit/c903985bf7e772e2d08275c1a95c8a55ab011577
- https://github.com/git/git/security/advisories/GHSA-hmg8-h7qf-7cxr
- https://lists.debian.org/debian-lts-announce/2025/01/msg00025.html
medium severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.19-3ubuntu2.2
- Fixed in: 2.2.19-3ubuntu2.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnupg2/gpgv@2.2.19-3ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."
Remediation
Upgrade Ubuntu:20.04 gnupg2 to version 2.2.19-3ubuntu2.4 or higher.
References
medium severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.19-3ubuntu2.2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnupg2/gpgv@2.2.19-3ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
Remediation
There is no fixed version for Ubuntu:20.04 gnupg2.
References
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@245.4-4ubuntu3.19 and systemd/libudev1@245.4-4ubuntu3.19
- Fixed in: 245.4-4ubuntu3.24+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libsystemd0@245.4-4ubuntu3.19
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libudev1@245.4-4ubuntu3.19
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process.
A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.
Remediation
Upgrade Ubuntu:20.04 systemd to version 245.4-4ubuntu3.24+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-4598
- https://access.redhat.com/security/cve/CVE-2025-4598
- https://bugzilla.redhat.com/show_bug.cgi?id=2369242
- https://www.openwall.com/lists/oss-security/2025/05/29/3
- http://www.openwall.com/lists/oss-security/2025/06/05/1
- http://www.openwall.com/lists/oss-security/2025/06/05/3
- https://blogs.oracle.com/linux/post/analysis-of-cve-2025-4598
- https://ciq.com/blog/the-real-danger-of-systemd-coredump-cve-2025-4598/
- https://www.openwall.com/lists/oss-security/2025/08/18/3
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://lists.debian.org/debian-lts-announce/2025/07/msg00022.html
- http://www.openwall.com/lists/oss-security/2025/08/18/3
- https://access.redhat.com/errata/RHSA-2025:22660
- https://access.redhat.com/errata/RHSA-2025:22868
- https://access.redhat.com/errata/RHSA-2025:23234
- https://access.redhat.com/errata/RHSA-2025:23227
- https://access.redhat.com/errata/RHSA-2026:0414
- https://access.redhat.com/errata/RHSA-2026:1652
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
There's a vulnerability in the libssh package where when a libssh consumer passes in an unexpectedly large input buffer to ssh_get_fingerprint_hash() function. In such cases the bin_to_base64() function can experience an integer overflow leading to a memory under allocation, when that happens it's possible that the program perform out of bounds write leading to a heap corruption. This issue affects only 32-bits builds of libssh.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-4877
- https://access.redhat.com/security/cve/CVE-2025-4877
- https://bugzilla.redhat.com/show_bug.cgi?id=2376193
- https://git.libssh.org/projects/libssh.git/commit/?h=stable-0.11&id=6fd9cc8ce3958092a1aae11f1f2e911b2747732d
- https://www.libssh.org/security/advisories/CVE-2025-4877.txt
medium severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.13
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In sshd in OpenSSH before 10.0, the DisableForwarding directive does not adhere to the documentation stating that it disables X11 and agent forwarding.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.13 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-32728
- https://ftp.openbsd.org/pub/OpenBSD/patches/7.6/common/013_ssh.patch.sig
- https://github.com/openssh/openssh-portable/commit/fc86875e6acb36401dfc1dfb6b628a9d1460f367
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2025-April/041879.html
- https://www.openssh.com/txt/release-10.0
- https://www.openssh.com/txt/release-7.4
- https://lists.debian.org/debian-lts-announce/2025/05/msg00008.html
- https://security.netapp.com/advisory/ntap-20250425-0002/
medium severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in libssh, where an uninitialized variable exists under certain conditions in the privatekey_from_file() function. This flaw can be triggered if the file specified by the filename doesn't exist and may lead to possible signing failures or heap corruption.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-4878
- https://access.redhat.com/security/cve/CVE-2025-4878
- https://bugzilla.redhat.com/show_bug.cgi?id=2376184
- https://git.libssh.org/projects/libssh.git/commit/?id=697650caa97eaf7623924c75f9fcfec6dd423cd1
- https://git.libssh.org/projects/libssh.git/commit/?id=b35ee876adc92a208d47194772e99f9c71e0bedb
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.44 and classified as problematic. This issue affects the function process_debug_info of the file binutils/dwarf.c of the component DWARF Section Handler. The manipulation leads to memory leak. Attacking locally is a requirement. The identifier of the patch is e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4. It is recommended to apply a patch to fix this issue.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11+esm1 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.12
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, local clones may end up hardlinking files into the target repository's object database when source and target repository reside on the same disk. If the source repository is owned by a different user, then those hardlinked files may be rewritten at any point in time by the untrusted user. Cloning local repositories will cause Git to either copy or hardlink files of the source repository into the target repository. This significantly speeds up such local clones compared to doing a "proper" clone and saves both disk space and compute time. When cloning a repository located on the same disk that is owned by a different user than the current user we also end up creating such hardlinks. These files will continue to be owned and controlled by the potentially-untrusted user and can be rewritten by them at will in the future. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.12 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-32020
- http://www.openwall.com/lists/oss-security/2024/05/14/2
- https://github.com/git/git/commit/1204e1a824c34071019fe106348eaa6d88f9528d
- https://github.com/git/git/commit/9e65df5eab274bf74c7b570107aacd1303a1e703
- https://github.com/git/git/security/advisories/GHSA-5rfh-556j-fhgj
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in GNU Binutils 2.43 and classified as problematic. Affected by this issue is the function link_order_scan of the file ld/ldelfgen.c of the component ld. The manipulation leads to memory leak. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-1148
- https://sourceware.org/bugzilla/attachment.cgi?id=15887
- https://sourceware.org/bugzilla/show_bug.cgi?id=32576
- https://vuldb.com/?ctiid.295052
- https://vuldb.com/?id.295052
- https://vuldb.com/?submit.485747
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0004/
medium severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. This affects the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component ld. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
medium severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
- Fixed in: 2.2.9-1ubuntu0.8+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.
Remediation
Upgrade Ubuntu:20.04 expat to version 2.2.9-1ubuntu0.8+esm1 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In Git for Windows, the Windows port of Git, no localized messages are shipped with the installer. As a consequence, Git is expected not to localize messages at all, and skips the gettext initialization. However, due to a change in MINGW-packages, the gettext() function's implicit initialization no longer uses the runtime prefix but uses the hard-coded path C:\mingw64\share\locale to look for localized messages. And since any authenticated user has the permission to create folders in C:\ (and since C:\mingw64 does not typically exist), it is possible for low-privilege users to place fake messages in that location where git.exe will pick them up in version 2.40.1.
This vulnerability is relatively hard to exploit and requires social engineering. For example, a legitimate message at the end of a clone could be maliciously modified to ask the user to direct their web browser to a malicious website, and the user might think that the message comes from Git and is legitimate. It does require local write access by the attacker, though, which makes this attack vector less likely. Version 2.40.1 contains a patch for this issue. Some workarounds are available. Do not work on a Windows machine with shared accounts, or alternatively create a C:\mingw64 folder and leave it empty. Users who have administrative rights may remove the permission to create folders in C:\.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-25815
- http://www.openwall.com/lists/oss-security/2023/04/25/2
- https://axcheron.github.io/exploit-101-format-strings/#writing-to-the-stack
- https://github.com/git-for-windows/git/releases/tag/v2.40.1.windows.1
- https://github.com/git-for-windows/git/security/advisories/GHSA-9w66-8mq8-5vm8
- https://github.com/msys2/MINGW-packages/pull/10461
- https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PI7FZ4NNR5S5J5K6AMVQBH2JFP6NE4L7/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RKOXOAZ42HLXHXTW6JZI4L5DAIYDTYCU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YFZWGQKB6MM5MNF2DLFTD7KS2KWPICKL/
- https://pubs.opengroup.org/onlinepubs/9699919799/functions/printf.html
- https://security.gentoo.org/glsa/202312-15
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.24
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When curl is told to use the Certificate Status Request TLS extension, often referred to as OCSP stapling, to verify that the server certificate is valid, it might fail to detect some OCSP problems and instead wrongly consider the response as fine. If the returned status reports another error than 'revoked' (like for example 'unauthorized') it is not treated as a bad certficate.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.24 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-8096
- https://curl.se/docs/CVE-2024-8096.html
- https://curl.se/docs/CVE-2024-8096.json
- https://hackerone.com/reports/2669852
- http://www.openwall.com/lists/oss-security/2024/09/11/1
- https://lists.debian.org/debian-lts-announce/2024/11/msg00008.html
- https://security.netapp.com/advisory/ntap-20241011-0005/
medium severity
new
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.25+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers.
Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.25+esm2 or higher.
References
medium severity
new
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates connections and not requests, contrary to how HTTP is designed to work.
An application that allows Negotiate authentication to a server (that responds
wanting Negotiate) with user1:password1 and then does another operation to
the same server also using Negotiate but with user2:password2 (while the
previous connection is still alive) - the second request wrongly reused the
same connection and since it then sees that the Negotiate negotiation is
already made, it just sends the request over that connection thinking it uses
the user2 credentials when it is in fact still using the connection
authenticated for user1...
The set of authentication methods to use is set with CURLOPT_HTTPAUTH.
Applications can disable libcurl's reuse of connections and thus mitigate this
problem, by using one of the following libcurl options to alter how
connections are or are not reused: CURLOPT_FRESH_CONNECT,
CURLOPT_MAXCONNECTS and CURLMOPT_MAX_HOST_CONNECTIONS (if using the
curl_multi API).
Remediation
There is no fixed version for Ubuntu:20.04 curl.
References
medium severity
new
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances.
If the hostname that the first request is redirected to has information in the
used .netrc file, with either of the machine or default keywords, curl
would pass on the bearer token set for the first host also to the second one.
Remediation
There is no fixed version for Ubuntu:20.04 curl.
References
medium severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.22
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When an application tells libcurl it wants to allow HTTP/2 server push, and the amount of received headers for the push surpasses the maximum allowed limit (1000), libcurl aborts the server push. When aborting, libcurl inadvertently does not free all the previously allocated headers and instead leaks the memory. Further, this error condition fails silently and is therefore not easily detected by an application.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.22 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-2398
- http://seclists.org/fulldisclosure/2024/Jul/18
- http://seclists.org/fulldisclosure/2024/Jul/19
- http://seclists.org/fulldisclosure/2024/Jul/20
- http://www.openwall.com/lists/oss-security/2024/03/27/3
- https://curl.se/docs/CVE-2024-2398.html
- https://curl.se/docs/CVE-2024-2398.json
- https://hackerone.com/reports/2402845
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/2D44YLAUFJU6BZ4XFG2FYV7SBKXB5IZ6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/GMD6UYKCCRCYETWQZUJ65ZRFULT6SHLI/
- https://security.netapp.com/advisory/ntap-20240503-0009/
- https://support.apple.com/kb/HT214118
- https://support.apple.com/kb/HT214119
- https://support.apple.com/kb/HT214120
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.2.9-1ubuntu0.6
- Fixed in: 2.2.9-1ubuntu0.8
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › expat/libexpat1@2.2.9-1ubuntu0.6
NVD Description
Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.
Remediation
Upgrade Ubuntu:20.04 expat to version 2.2.9-1ubuntu0.8 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.14+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git GUI allows you to use the Git source control management tools via a GUI. When a user clones an untrusted repository and is tricked into editing a file located in a maliciously named directory in the repository, then Git GUI can create and overwrite files for which the user has write permission. This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.14+esm3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-46835
- https://github.com/j6t/git-gui/compare/dcda716dbc9c90bcac4611bd1076747671ee0906..a437f5bc93330a70b42a230e52f3bd036ca1b1da
- https://github.com/j6t/git-gui/security/advisories/GHSA-xfx7-68v4-v8fg
- https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
- http://www.openwall.com/lists/oss-security/2025/07/08/4
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.14+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. The wincred credential helper uses a static buffer (target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it with wcsncat(), leading to potential buffer overflows. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.14+esm1 or higher.
References
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.25.1-1ubuntu3.8 and git/git-man@1:2.25.1-1ubuntu3.8
- Fixed in: 1:2.25.1-1ubuntu3.14+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git@1:2.25.1-1ubuntu3.8
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › git/git-man@1:2.25.1-1ubuntu3.8
NVD Description
Note: Versions mentioned in the description apply only to the upstream git package and not the git package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Gitk is a Tcl/Tk based Git history browser. Starting with 1.7.0, when a user clones an untrusted repository and runs gitk without additional command arguments, files for which the user has write permission can be created and truncated. The option Support per-file encoding must have been enabled before in Gitk's Preferences. This option is disabled by default. The same happens when Show origin of this line is used in the main window (regardless of whether Support per-file encoding is enabled or not). This vulnerability is fixed in 2.43.7, 2.44.4, 2.45.4, 2.46.4, 2.47.3, 2.48.2, 2.49.1, and 2.50.1.
Remediation
Upgrade Ubuntu:20.04 git to version 1:2.25.1-1ubuntu3.14+esm3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-27613
- https://github.com/j6t/gitk/compare/465f03869ae11acd04abfa1b83c67879c867410c..026c397d911cde55924d7eb1311d0fd6e2e105d5
- https://github.com/j6t/gitk/compare/7dd272eca153058da2e8d5b9960bbbf0b4f0cbaa..67a128b91e25978a15f9f7e194d81b441d603652
- https://github.com/j6t/gitk/security/advisories/GHSA-f3cw-xrj3-wr2v
- https://lists.debian.org/debian-lts-announce/2025/10/msg00003.html
- http://www.openwall.com/lists/oss-security/2025/07/08/4
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.15
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The iconv() function in the GNU C Library versions 2.39 and older may overflow the output buffer passed to it by up to 4 bytes when converting strings to the ISO-2022-CN-EXT character set, which may be used to crash an application or overwrite a neighbouring variable.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.15 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-2961
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p1
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p2
- https://www.ambionics.io/blog/iconv-cve-2024-2961-p3
- http://www.openwall.com/lists/oss-security/2024/04/17/9
- http://www.openwall.com/lists/oss-security/2024/04/18/4
- http://www.openwall.com/lists/oss-security/2024/04/24/2
- http://www.openwall.com/lists/oss-security/2024/05/27/1
- http://www.openwall.com/lists/oss-security/2024/05/27/2
- http://www.openwall.com/lists/oss-security/2024/05/27/3
- http://www.openwall.com/lists/oss-security/2024/05/27/4
- http://www.openwall.com/lists/oss-security/2024/05/27/5
- http://www.openwall.com/lists/oss-security/2024/05/27/6
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/05/msg00001.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BTJFBGHDYG5PEIFD5WSSSKSFZ2AZWC5N/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/P3I4KYS6EU6S7QZ47WFNTPVAHFIUQNEL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YAMJQI3Y6BHWV3CUTYBXOZONCUJNOB2Z/
- https://security.netapp.com/advisory/ntap-20240531-0002/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0004
- https://github.com/ambionics/cnext-exploits
- https://github.com/projectdiscovery/nuclei-templates/blob/main/dast/cves/2024/CVE-2024-2961.yaml
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.16
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
nscd: Stack-based buffer overflow in netgroup cache
If the Name Service Cache Daemon's (nscd) fixed size cache is exhausted by client requests then a subsequent client request for netgroup data may result in a stack-based buffer overflow. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.16 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-33599
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0011/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0005
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.16
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
nscd: Null pointer crashes after notfound response
If the Name Service Cache Daemon's (nscd) cache fails to add a not-found netgroup response to the cache, the client request can result in a null pointer dereference. This flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.16 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-33600
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0013/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0006
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.16
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
nscd: netgroup cache may terminate daemon on memory allocation failure
The Name Service Cache Daemon's (nscd) netgroup cache uses xmalloc or xrealloc and these functions may terminate the process due to a memory allocation failure resulting in a denial of service to the clients. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.16 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-33601
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0014/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0007
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.16
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
nscd: netgroup cache assumes NSS callback uses in-buffer strings
The Name Service Cache Daemon's (nscd) netgroup cache can corrupt memory when the NSS callback does not store all strings in the provided buffer. The flaw was introduced in glibc 2.15 when the cache was added to nscd.
This vulnerability is only present in the nscd binary.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.16 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-33602
- http://www.openwall.com/lists/oss-security/2024/07/22/5
- https://lists.debian.org/debian-lts-announce/2024/06/msg00026.html
- https://security.netapp.com/advisory/ntap-20240524-0012/
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2024-0008
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.17
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.17 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-0395
- https://sourceware.org/bugzilla/show_bug.cgi?id=32582
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2025-0001
- https://sourceware.org/pipermail/libc-announce/2025/000044.html
- https://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/23/2
- https://security.netapp.com/advisory/ntap-20250228-0006/
- http://www.openwall.com/lists/oss-security/2025/04/13/1
- http://www.openwall.com/lists/oss-security/2025/04/24/7
- https://lists.debian.org/debian-lts-announce/2025/04/msg00039.html
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.18+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.18+esm1 or higher.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-4802
- https://sourceware.org/bugzilla/show_bug.cgi?id=32976
- https://sourceware.org/cgit/glibc/commit/?id=1e18586c5820e329f741d5c710275e165581380e
- http://www.openwall.com/lists/oss-security/2025/05/16/7
- http://www.openwall.com/lists/oss-security/2025/05/17/2
- https://lists.debian.org/debian-lts-announce/2025/05/msg00033.html
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.18+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The regcomp function in the GNU C library version from 2.4 to 2.41 is subject to a double free if some previous allocation fails. It can be accomplished either by a malloc failure or by using an interposed malloc that injects random malloc failures. The double free can allow buffer manipulation depending of how the regex is constructed. This issue affects all architectures and ABIs supported by the GNU C library.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.18+esm1 or higher.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.18+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption.
Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc.
Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.18+esm1 or higher.
References
medium severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.18+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.18+esm1 or higher.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.7
- Fixed in: 3.6.13-2ubuntu1.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnutls28/libgnutls30@3.6.13-2ubuntu1.7
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnutls28 package and not the gnutls28 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in GnuTLS. The Minerva attack is a cryptographic vulnerability that exploits deterministic behavior in systems like GnuTLS, leading to side-channel leaks. In specific scenarios, such as when using the GNUTLS_PRIVKEY_FLAG_REPRODUCIBLE flag, it can result in a noticeable step in nonce size from 513 to 512 bits, exposing a potential timing side-channel.
Remediation
Upgrade Ubuntu:20.04 gnutls28 to version 3.6.13-2ubuntu1.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-28834
- http://www.openwall.com/lists/oss-security/2024/03/22/1
- http://www.openwall.com/lists/oss-security/2024/03/22/2
- https://people.redhat.com/~hkario/marvin/
- https://security.netapp.com/advisory/ntap-20240524-0004/
- https://access.redhat.com/errata/RHSA-2024:1784
- https://access.redhat.com/errata/RHSA-2024:1879
- https://access.redhat.com/errata/RHSA-2024:1997
- https://access.redhat.com/errata/RHSA-2024:2044
- https://access.redhat.com/errata/RHSA-2024:2570
- https://access.redhat.com/errata/RHSA-2024:2889
- https://access.redhat.com/security/cve/CVE-2024-28834
- https://bugzilla.redhat.com/show_bug.cgi?id=2269228
- https://lists.debian.org/debian-lts-announce/2024/09/msg00019.html
- https://lists.gnupg.org/pipermail/gnutls-help/2024-March/004845.html
- https://minerva.crocs.fi.muni.cz/
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22 (with incremental propagation), there is an integer overflow for a large update size to resize() in kdb_log.c. An authenticated attacker can cause an out-of-bounds write and kadmind daemon crash.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.9 or higher.
References
medium severity
- Vulnerable module: less
- Introduced through: less@551-1ubuntu0.1
- Fixed in: 551-1ubuntu0.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › less@551-1ubuntu0.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream less package and not the less package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
less through 653 allows OS command execution via a newline character in the name of a file, because quoting is mishandled in filename.c. Exploitation typically requires use with attacker-controlled file names, such as the files extracted from an untrusted archive. Exploitation also requires the LESSOPEN environment variable, but this is set by default in many common cases.
Remediation
Upgrade Ubuntu:20.04 less to version 551-1ubuntu0.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-32487
- http://www.openwall.com/lists/oss-security/2024/04/15/1
- https://github.com/gwsw/less/commit/007521ac3c95bc76e3d59c6dbfe75d06c8075c33
- https://lists.debian.org/debian-lts-announce/2024/05/msg00018.html
- https://security.netapp.com/advisory/ntap-20240605-0009/
- https://www.openwall.com/lists/oss-security/2024/04/12/5
- https://www.openwall.com/lists/oss-security/2024/04/13/2
medium severity
new
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to 1.6.52, an out-of-bounds read vulnerability in libpng's simplified API allows reading up to 1012 bytes beyond the png_sRGB_base[512] array when processing valid palette PNG images with partial transparency and gamma correction. The PNG files that trigger this vulnerability are valid per the PNG specification; the bug is in libpng's internal state management. Upgrade to libpng 1.6.52 or later.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-66293
- https://github.com/pnggroup/libpng/commit/788a624d7387a758ffd5c7ab010f1870dea753a1
- https://github.com/pnggroup/libpng/commit/a05a48b756de63e3234ea6b3b938b8f5f862484a
- https://github.com/pnggroup/libpng/security/advisories/GHSA-9mpm-9pxh-mg4f
- http://www.openwall.com/lists/oss-security/2025/12/03/6
- http://www.openwall.com/lists/oss-security/2025/12/03/7
- http://www.openwall.com/lists/oss-security/2025/12/03/8
- https://github.com/pnggroup/libpng/issues/764
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, there is a heap buffer overflow vulnerability in the libpng simplified API function png_image_finish_read when processing 16-bit interlaced PNGs with 8-bit output format. Attacker-crafted interlaced PNG files cause heap writes beyond allocated buffer bounds. This issue has been patched in version 1.6.51.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-65018
- https://github.com/pnggroup/libpng/commit/16b5e3823918840aae65c0a6da57c78a5a496a4d
- https://github.com/pnggroup/libpng/commit/218612ddd6b17944e21eda56caf8b4bf7779d1ea
- https://github.com/pnggroup/libpng/pull/757
- https://github.com/pnggroup/libpng/issues/755
- https://github.com/pnggroup/libpng/security/advisories/GHSA-7wv6-48j4-hj3g
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. Prior to version 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_do_quantize function when processing PNG files with malformed palette indices. The vulnerability occurs when palette_lookup array bounds are not validated against externally-supplied image data, allowing an attacker to craft a PNG file with out-of-range palette indices that trigger out-of-bounds memory access. This issue has been patched in version 1.6.51.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm1 or higher.
References
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, a heap buffer over-read vulnerability exists in libpng's png_write_image_8bit function when processing 8-bit images through the simplified write API with convert_to_8bit enabled. The vulnerability affects 8-bit grayscale+alpha, RGB/RGBA, and images with incomplete row data. A conditional guard incorrectly allows 8-bit input to enter code expecting 16-bit input, causing reads up to 2 bytes beyond allocated buffer boundaries. This issue has been patched in version 1.6.51.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm1 or higher.
References
medium severity
- Vulnerable module: libpng1.6/libpng16-16
- Introduced through: libpng1.6/libpng16-16@1.6.37-2
- Fixed in: 1.6.37-2ubuntu0.1~esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libpng1.6/libpng16-16@1.6.37-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libpng1.6 package and not the libpng1.6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
LIBPNG is a reference library for use in applications that read, create, and manipulate PNG (Portable Network Graphics) raster image files. From version 1.6.0 to before 1.6.51, an out-of-bounds read vulnerability exists in png_image_read_composite when processing palette images with PNG_FLAG_OPTIMIZE_ALPHA enabled. The palette compositing code in png_init_read_transformations incorrectly applies background compositing during premultiplication, violating the invariant component ≤ alpha × 257 required by the simplified PNG API. This issue has been patched in version 1.6.51.
Remediation
Upgrade Ubuntu:20.04 libpng1.6 to version 1.6.37-2ubuntu0.1~esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-64720
- https://github.com/pnggroup/libpng/commit/08da33b4c88cfcd36e5a706558a8d7e0e4773643
- https://github.com/pnggroup/libpng/issues/686
- https://github.com/pnggroup/libpng/pull/751
- https://github.com/pnggroup/libpng/security/advisories/GHSA-hfc7-ph9c-wcww
medium severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm3 or higher.
References
medium severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm3 or higher.
References
medium severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm3 or higher.
References
medium severity
new
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.16.0-2
- Fixed in: 4.16.0-2ubuntu0.1+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libtasn1-6@4.16.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.
Remediation
Upgrade Ubuntu:20.04 libtasn1-6 to version 4.16.0-2ubuntu0.1+esm1 or higher.
References
medium severity
- Vulnerable module: nghttp2/libnghttp2-14
- Introduced through: nghttp2/libnghttp2-14@1.40.0-1build1
- Fixed in: 1.40.0-1ubuntu0.3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › nghttp2/libnghttp2-14@1.40.0-1build1
NVD Description
Note: Versions mentioned in the description apply only to the upstream nghttp2 package and not the nghttp2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. The nghttp2 library prior to version 1.61.0 keeps reading the unbounded number of HTTP/2 CONTINUATION frames even after a stream is reset to keep HPACK context in sync. This causes excessive CPU usage to decode HPACK stream. nghttp2 v1.61.0 mitigates this vulnerability by limiting the number of CONTINUATION frames it accepts per stream. There is no workaround for this vulnerability.
Remediation
Upgrade Ubuntu:20.04 nghttp2 to version 1.40.0-1ubuntu0.3 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-28182
- https://lists.debian.org/debian-lts-announce/2024/09/msg00041.html
- http://www.openwall.com/lists/oss-security/2024/04/03/16
- https://github.com/nghttp2/nghttp2/commit/00201ecd8f982da3b67d4f6868af72a1b03b14e0
- https://github.com/nghttp2/nghttp2/commit/d71a4668c6bead55805d18810d633fbb98315af9
- https://github.com/nghttp2/nghttp2/security/advisories/GHSA-x6x3-gv8h-m57q
- https://lists.debian.org/debian-lts-announce/2024/04/msg00026.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AGOME6ZXJG7664IPQNVE3DL67E3YP3HY/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/J6ZMXUGB66VAXDW5J6QSTHM5ET25FGSA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PXJO2EASHM2OQQLGVDY5ZSO7UVDVHTDK/
- https://www.kb.cert.org/vuls/id/421644
medium severity
new
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.13+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.13+esm1 or higher.
References
medium severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.
Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.
Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-9230
- https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45
- https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280
- https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def
- https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd
- https://github.com/openssl/openssl/commit/bae259a211ada6315dc50900686daaaaaa55f482
- https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3
- https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba
- https://openssl-library.org/news/secadv/20250930.txt
- https://lists.debian.org/debian-lts-announce/2025/10/msg00001.html
- http://www.openwall.com/lists/oss-security/2025/09/30/5
medium severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
- Fixed in: 3.31.1-4ubuntu0.7
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › sqlite3/libsqlite3-0@3.31.1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2025-29088. Reason: This record is a duplicate of CVE-2025-29088. Notes: All CVE users should reference CVE-2025-29088 instead of this record. All references and descriptions in this record have been removed to prevent accidental usage.
Remediation
Upgrade Ubuntu:20.04 sqlite3 to version 3.31.1-4ubuntu0.7 or higher.
References
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.30+dfsg-7ubuntu0.20.04.2
- Fixed in: 1.30+dfsg-7ubuntu0.20.04.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › tar@1.30+dfsg-7ubuntu0.20.04.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In GNU tar before 1.35, mishandled extension attributes in a PAX archive can lead to an application crash in xheader.c.
Remediation
Upgrade Ubuntu:20.04 tar to version 1.30+dfsg-7ubuntu0.20.04.4 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-39804
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058079
- https://git.savannah.gnu.org/cgit/tar.git/commit/?id=a339f05cd269013fa133d2f148d73f6f7d4247e4
- https://git.savannah.gnu.org/cgit/tar.git/tree/src/xheader.c?h=release_1_34#n1723
- https://lists.debian.org/debian-lts-announce/2024/03/msg00008.html
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.30+dfsg-7ubuntu0.20.04.2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › tar@1.30+dfsg-7ubuntu0.20.04.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages). NOTE: the official GNU Tar manual has an otherwise-empty directory for each "tar xf" in its Security Rules of Thumb; however, third-party advice leads users to run "tar xf" more than once into the same directory.
Remediation
There is no fixed version for Ubuntu:20.04 tar.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-45582
- https://github.com/i900008/vulndb/blob/main/Gnu_tar_vuln.md
- https://www.gnu.org/software/tar/
- https://lists.gnu.org/archive/html/bug-tar/2025-08/msg00012.html
- https://www.gnu.org/software/tar/manual/html_node/Integrity.html
- https://www.gnu.org/software/tar/manual/html_node/Security-rules-of-thumb.html
- http://www.openwall.com/lists/oss-security/2025/11/01/6
medium severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.34-0.1ubuntu9.3, util-linux/fdisk@2.34-0.1ubuntu9.3 and others
- Fixed in: 2.34-0.1ubuntu9.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/fdisk@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/libblkid1@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/libfdisk1@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/libmount1@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/libsmartcols1@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/libuuid1@2.34-0.1ubuntu9.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › util-linux/mount@2.34-0.1ubuntu9.3
NVD Description
Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
wall in util-linux through 2.40, often installed with setgid tty permissions, allows escape sequences to be sent to other users' terminals through argv. (Specifically, escape sequences received from stdin are blocked, but escape sequences received from argv are not blocked.) There may be plausible scenarios where this leads to account takeover.
Remediation
Upgrade Ubuntu:20.04 util-linux to version 2.34-0.1ubuntu9.6 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-28085
- http://seclists.org/fulldisclosure/2024/Mar/35
- http://www.openwall.com/lists/oss-security/2024/03/27/5
- http://www.openwall.com/lists/oss-security/2024/03/27/6
- http://www.openwall.com/lists/oss-security/2024/03/27/7
- http://www.openwall.com/lists/oss-security/2024/03/27/8
- http://www.openwall.com/lists/oss-security/2024/03/27/9
- http://www.openwall.com/lists/oss-security/2024/03/28/1
- http://www.openwall.com/lists/oss-security/2024/03/28/2
- http://www.openwall.com/lists/oss-security/2024/03/28/3
- https://github.com/skyler-ferrante/CVE-2024-28085
- https://github.com/util-linux/util-linux/security/advisories/GHSA-xv2h-c6ww-mrjq
- https://lists.debian.org/debian-lts-announce/2024/04/msg00005.html
- https://mirrors.edge.kernel.org/pub/linux/utils/util-linux/
- https://people.rit.edu/sjf5462/6831711781/wall_2_27_2024.txt
- https://security.netapp.com/advisory/ntap-20240531-0003/
- https://www.openwall.com/lists/oss-security/2024/03/27/5
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The mq_notify function in the GNU C Library (aka glibc) versions 2.32 and 2.33 has a use-after-free. It may use the notification thread attributes object (passed through its struct sigevent parameter) after it has been freed by the caller, leading to a denial of service (application crash) or possibly unspecified other impact.
Remediation
There is no fixed version for Ubuntu:20.04 glibc.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-33574
- https://security.netapp.com/advisory/ntap-20210629-0005/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/RBUUWUGXVILQXVWEOU7N42ICHPJNAEUP/
- https://security.gentoo.org/glsa/202107-07
- https://sourceware.org/bugzilla/show_bug.cgi?id=27896
- https://sourceware.org/bugzilla/show_bug.cgi?id=27896#c1
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KJYYIMDDYOHTP2PORLABTOHYQYYREZDD/
- https://lists.debian.org/debian-lts-announce/2022/10/msg00021.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KJYYIMDDYOHTP2PORLABTOHYQYYREZDD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RBUUWUGXVILQXVWEOU7N42ICHPJNAEUP/
low severity
new
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.16.0-2
- Fixed in: 4.16.0-2ubuntu0.1+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libtasn1-6@4.16.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Libtasn1 before 4.19.0 has an ETYPE_OK off-by-one array size check that affects asn1_encode_simple_der.
Remediation
Upgrade Ubuntu:20.04 libtasn1-6 to version 4.16.0-2ubuntu0.1+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-46848
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AV4SHDJF2XLB4CUPTBPQQ6CLGZ5LKXPZ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/ECM2ELTVRYV4BZ5L5GMIRQE27RFHPAQ6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGO7XST4EIJGX4B2ITZCYSWM24534BSU/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/V5LWOGF7QRMNFRUCZY6TDYQJVFI6MOQ2/
- https://bugs.gentoo.org/866237
- https://gitlab.com/gnutls/libtasn1/-/commit/44a700d2051a666235748970c2df047ff207aeb5
- https://gitlab.com/gnutls/libtasn1/-/issues/32
- https://lists.debian.org/debian-lts-announce/2023/01/msg00003.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/AV4SHDJF2XLB4CUPTBPQQ6CLGZ5LKXPZ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ECM2ELTVRYV4BZ5L5GMIRQE27RFHPAQ6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/OGO7XST4EIJGX4B2ITZCYSWM24534BSU/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/V5LWOGF7QRMNFRUCZY6TDYQJVFI6MOQ2/
- https://security.netapp.com/advisory/ntap-20221118-0006/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-27533
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1891474
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0011/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde () character to be wrongly replaced when used as a prefix in the first path element, in addition to its intended use as the first element to indicate a path relative to the user's home directory. Attackers can exploit this flaw to bypass filtering or execute arbitrary code by crafting a path like /2/foo while accessing a server with a specific user.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-27534
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1892351
- https://lists.debian.org/debian-lts-announce/2024/03/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0012/
low severity
- Vulnerable module: ncurses/libncurses6
- Introduced through: ncurses/libncurses6@6.2-0ubuntu2, ncurses/libncursesw6@6.2-0ubuntu2 and others
- Fixed in: 6.2-0ubuntu2.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncurses6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncursesw6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libtinfo6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-base@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-bin@6.2-0ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An issue was discovered in ncurses through v6.2-1. _nc_captoinfo in captoinfo.c has a heap-based buffer overflow.
Remediation
Upgrade Ubuntu:20.04 ncurses to version 6.2-0ubuntu2.1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-39537
- http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/devel/ncurses/patches/patch-ncurses_tinfo_captoinfo.c?rev=1.1&content-type=text/x-cvsweb-markup
- https://lists.gnu.org/archive/html/bug-ncurses/2020-08/msg00006.html
- https://lists.gnu.org/archive/html/bug-ncurses/2021-10/msg00023.html
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- http://seclists.org/fulldisclosure/2022/Oct/43
- http://seclists.org/fulldisclosure/2022/Oct/45
- https://support.apple.com/kb/HT213443
- https://support.apple.com/kb/HT213444
- https://support.apple.com/kb/HT213488
- https://security.netapp.com/advisory/ntap-20230427-0012/
- https://lists.debian.org/debian-lts-announce/2023/12/msg00004.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
stab_xcoff_builtin_type in stabs.c in GNU Binutils through 2.37 allows attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact, as demonstrated by an out-of-bounds write. NOTE: this issue exists because of an incorrect fix for CVE-2018-12699.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.6 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-45078
- https://sourceware.org/bugzilla/show_bug.cgi?id=28694
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=161e87d12167b1e36193385485c1f6ce92f74f02
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UQBH244M5PV6S6UMHUTCVCWFZDX7Y4M6/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/UUHLDDT3HH7YEY6TX7IJRGPJUTNNVEL3/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UQBH244M5PV6S6UMHUTCVCWFZDX7Y4M6/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/UUHLDDT3HH7YEY6TX7IJRGPJUTNNVEL3/
- https://security.gentoo.org/glsa/202208-30
- https://security.netapp.com/advisory/ntap-20220107-0002/
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git%3Bh=161e87d12167b1e36193385485c1f6ce92f74f02
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@245.4-4ubuntu3.19 and systemd/libudev1@245.4-4ubuntu3.19
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libsystemd0@245.4-4ubuntu3.19
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libudev1@245.4-4ubuntu3.19
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
systemd before 247 does not adequately block local privilege escalation for some Sudo configurations, e.g., plausible sudoers files in which the "systemctl status" command may be executed. Specifically, systemd does not set LESSSECURE to 1, and thus other programs may be launched from the less program. This presents a substantial security risk when running systemctl from Sudo, because less executes as root when the terminal size is too small to show the complete systemctl output.
Remediation
There is no fixed version for Ubuntu:20.04 systemd.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-26604
- https://medium.com/@zenmoviefornotification/saidov-maxim-cve-2023-26604-c1232a526ba7
- http://packetstormsecurity.com/files/174130/systemd-246-Local-Root-Privilege-Escalation.html
- https://blog.compass-security.com/2012/10/dangerous-sudoers-entries-part-2-insecure-functionality/
- https://github.com/systemd/systemd/blob/main/NEWS#L4335-L4340
- https://lists.debian.org/debian-lts-announce/2023/03/msg00032.html
- https://medium.com/%40zenmoviefornotification/saidov-maxim-cve-2023-26604-c1232a526ba7
- https://security.netapp.com/advisory/ntap-20230505-0009/
- https://www.exploit-db.com/exploits/51674
low severity
- Vulnerable module: openldap/libldap-2.4-2
- Introduced through: openldap/libldap-2.4-2@2.4.49+dfsg-2ubuntu1.9 and openldap/libldap-common@2.4.49+dfsg-2ubuntu1.9
- Fixed in: 2.4.49+dfsg-2ubuntu1.10
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openldap/libldap-2.4-2@2.4.49+dfsg-2ubuntu1.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openldap/libldap-common@2.4.49+dfsg-2ubuntu1.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in openldap. This security flaw causes a null pointer dereference in ber_memalloc_x() function.
Remediation
Upgrade Ubuntu:20.04 openldap to version 2.4.49+dfsg-2ubuntu1.10 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-2953
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://access.redhat.com/security/cve/CVE-2023-2953
- https://bugs.openldap.org/show_bug.cgi?id=9904
- https://security.netapp.com/advisory/ntap-20230703-0005/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-69421
- https://github.com/openssl/openssl/commit/3524a29271f8191b8fd8a5257eb05173982a097b
- https://github.com/openssl/openssl/commit/36ecb4960872a4ce04bf6f1e1f4e78d75ec0c0c7
- https://github.com/openssl/openssl/commit/4bbc8d41a72c842ce4077a8a3eccd1109aaf74bd
- https://github.com/openssl/openssl/commit/643986985cd1c21221f941129d76fe0c2785aeb3
- https://github.com/openssl/openssl/commit/a2dbc539f0f9cc63832709fa5aa33ad9495eb19c
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A security vulnerability has been identified in all supported versions
of OpenSSL related to the verification of X.509 certificate chains that include policy constraints. Attackers may be able to exploit this vulnerability by creating a malicious certificate chain that triggers exponential use of computational resources, leading to a denial-of-service (DoS) attack on affected systems.
Policy processing is disabled by default but can be enabled by passing
the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-0464
- https://security.netapp.com/advisory/ntap-20230406-0006/
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2017771e2db3e2b96f89bbe8766c3209f6a99545
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=2dcd4f1e3115f38cefa43e3efbe9b801c27e642e
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=879f7080d7e141f415c79eaa3a8ac4a3dad0348b
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=959c59c7a0164117e7f8366466a32bb1f8d77ff1
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://www.couchbase.com/alerts/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230322.txt
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › patch@2.7.6-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.
Remediation
There is no fixed version for Ubuntu:20.04 patch.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-6952
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-6952
- https://security-tracker.debian.org/tracker/CVE-2018-6952
- https://security.gentoo.org/glsa/201904-17
- https://savannah.gnu.org/bugs/index.php?53133
- https://access.redhat.com/errata/RHSA-2019:2033
- http://www.securityfocus.com/bid/103047
low severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.34-7ubuntu0.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pcre2/libpcre2-8-0@10.34-7ubuntu0.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.
Remediation
There is no fixed version for Ubuntu:20.04 pcre2.
References
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-12ubuntu0.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › pcre3/libpcre3@2:8.39-12ubuntu0.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream pcre3 package and not the pcre3 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In PCRE 8.41, the OP_KETRMAX feature in the match function in pcre_exec.c allows stack exhaustion (uncontrolled recursion) when processing a crafted regular expression.
Remediation
There is no fixed version for Ubuntu:20.04 pcre3.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-11164
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11164
- https://security-tracker.debian.org/tracker/CVE-2017-11164
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://openwall.com/lists/oss-security/2017/07/11/3
- http://www.securityfocus.com/bid/99575
- http://www.openwall.com/lists/oss-security/2023/04/11/1
- http://www.openwall.com/lists/oss-security/2023/04/12/1
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: ncurses/libncurses6
- Introduced through: ncurses/libncurses6@6.2-0ubuntu2, ncurses/libncursesw6@6.2-0ubuntu2 and others
- Fixed in: 6.2-0ubuntu2.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncurses6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncursesw6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libtinfo6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-base@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-bin@6.2-0ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
ncurses 6.3 before patch 20220416 has an out-of-bounds read and segmentation violation in convert_strings in tinfo/read_entry.c in the terminfo library.
Remediation
Upgrade Ubuntu:20.04 ncurses to version 6.2-0ubuntu2.1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-29458
- http://seclists.org/fulldisclosure/2022/Oct/28
- http://seclists.org/fulldisclosure/2022/Oct/41
- https://lists.debian.org/debian-lts-announce/2022/10/msg00037.html
- https://lists.gnu.org/archive/html/bug-ncurses/2022-04/msg00014.html
- https://lists.gnu.org/archive/html/bug-ncurses/2022-04/msg00016.html
- https://support.apple.com/kb/HT213488
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
sshd in OpenSSH 6.2 through 8.x before 8.8, when certain non-default configurations are used, allows privilege escalation because supplemental groups are not initialized as expected. Helper programs for AuthorizedKeysCommand and AuthorizedPrincipalsCommand may run with privileges associated with group memberships of the sshd process, if the configuration specifies running the command as a different user.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2021-41617
- https://bugzilla.suse.com/show_bug.cgi?id=1190975
- https://security.netapp.com/advisory/ntap-20211014-0004/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/6XJIONMHMKZDTMH6BQR5TNLF2WDCGWED/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KVI7RWM2JLNMWTOFK6BDUSGNOIPZYPUT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/W44V2PFQH5YLRN6ZJTVRKAD7CU6CYYET/
- https://www.openssh.com/security.html
- https://www.openssh.com/txt/release-8.8
- https://www.openwall.com/lists/oss-security/2021/09/26/1
- https://www.oracle.com/security-alerts/cpuapr2022.html
- https://www.oracle.com/security-alerts/cpujul2022.html
- https://www.starwindsoftware.com/security/sw-20220805-0001/
- https://www.tenable.com/plugins/nessus/154174
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6XJIONMHMKZDTMH6BQR5TNLF2WDCGWED/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KVI7RWM2JLNMWTOFK6BDUSGNOIPZYPUT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/W44V2PFQH5YLRN6ZJTVRKAD7CU6CYYET/
- https://www.debian.org/security/2023/dsa-5586
- https://lists.debian.org/debian-lts-announce/2023/12/msg00017.html
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@8.30-3ubuntu2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › coreutils@8.30-3ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
Remediation
There is no fixed version for Ubuntu:20.04 coreutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-2781
- https://security-tracker.debian.org/tracker/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.openwall.com/lists/oss-security/2016/02/28/2
- http://www.openwall.com/lists/oss-security/2016/02/28/3
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: ncurses/libncurses6
- Introduced through: ncurses/libncurses6@6.2-0ubuntu2, ncurses/libncursesw6@6.2-0ubuntu2 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncurses6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncursesw6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libtinfo6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-base@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-bin@6.2-0ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().
Remediation
There is no fixed version for Ubuntu:20.04 ncurses.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-50495
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00020.html
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00029.html
- https://security.netapp.com/advisory/ntap-20240119-0008/
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
- Fixed in: 2.34-6ubuntu1.11
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.
Remediation
Upgrade Ubuntu:20.04 binutils to version 2.34-6ubuntu1.11 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-1153
- https://sourceware.org/bugzilla/show_bug.cgi?id=32603
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150
- https://vuldb.com/?ctiid.295057
- https://vuldb.com/?id.295057
- https://vuldb.com/?submit.489991
- https://www.gnu.org/
- https://security.netapp.com/advisory/ntap-20250404-0005/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An authentication bypass vulnerability exists libcurl <8.0.0 in the connection reuse feature which can reuse previously established connections with incorrect user permissions due to a failure to check for changes in the CURLOPT_GSSAPI_DELEGATION option. This vulnerability affects krb5/kerberos/negotiate/GSSAPI transfers and could potentially result in unauthorized access to sensitive information. The safest option is to not reuse connections if the CURLOPT_GSSAPI_DELEGATION option has been changed.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-27536
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1895135
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0010/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.19
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with xn-- and should not be allowed to pattern match, but the wildcard check in curl could still check for x*, which would match even though the IDN name most likely contained nothing even resembling an x.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.19 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-28321
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://hackerone.com/reports/1950627
- https://lists.debian.org/debian-lts-announce/2023/10/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230609-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.14
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw has been identified in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.14 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-4813
- http://www.openwall.com/lists/oss-security/2023/10/03/8
- https://security.netapp.com/advisory/ntap-20231110-0003/
- https://access.redhat.com/errata/RHBA-2024:2413
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5455
- https://access.redhat.com/errata/RHSA-2023:7409
- https://access.redhat.com/security/cve/CVE-2023-4813
- https://bugzilla.redhat.com/show_bug.cgi?id=2237798
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.31-0ubuntu9.9, glibc/libc6@2.31-0ubuntu9.9 and others
- Fixed in: 2.31-0ubuntu9.14
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc-bin@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/libc6@2.31-0ubuntu9.9
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › glibc/locales@2.31-0ubuntu9.9
NVD Description
Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw has been identified in glibc. In an extremely rare situation, the getaddrinfo function may access memory that has been freed, resulting in an application crash. This issue is only exploitable when a NSS module implements only the nss_gethostbyname2_r and nss_getcanonname_r hooks without implementing the nss*_gethostbyname3_r hook. The resolved name should return a large number of IPv6 and IPv4, and the call to the getaddrinfo function should have the AF_INET6 address family with AI_CANONNAME, AI_ALL and AI_V4MAPPED as flags.
Remediation
Upgrade Ubuntu:20.04 glibc to version 2.31-0ubuntu9.14 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-4806
- http://www.openwall.com/lists/oss-security/2023/10/03/4
- http://www.openwall.com/lists/oss-security/2023/10/03/5
- http://www.openwall.com/lists/oss-security/2023/10/03/6
- http://www.openwall.com/lists/oss-security/2023/10/03/8
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4DBUQRRPB47TC3NJOUIBVWUGFHBJAFDL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/DFG4P76UHHZEWQ26FWBXG76N2QLKKPZA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NDAQWHTSVOCOZ5K6KPIWKRT3JX4RTZUR/
- https://security.gentoo.org/glsa/202310-03
- https://security.netapp.com/advisory/ntap-20240125-0008/
- https://access.redhat.com/errata/RHBA-2024:2413
- https://access.redhat.com/errata/RHSA-2023:5453
- https://access.redhat.com/errata/RHSA-2023:5455
- https://access.redhat.com/errata/RHSA-2023:7409
- https://access.redhat.com/security/cve/CVE-2023-4806
- https://bugzilla.redhat.com/show_bug.cgi?id=2237782
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@245.4-4ubuntu3.19 and systemd/libudev1@245.4-4ubuntu3.19
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libsystemd0@245.4-4ubuntu3.19
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › systemd/libudev1@245.4-4ubuntu3.19
NVD Description
Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability was found in systemd-resolved. This issue may allow systemd-resolved to accept records of DNSSEC-signed domains even when they have no signature, allowing man-in-the-middles (or the upstream DNS resolver) to manipulate records.
Remediation
There is no fixed version for Ubuntu:20.04 systemd.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-7008
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/4GMDEG5PKONWNHOEYSUDRT6JEOISRMN2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QHNBXGKJWISJETTTDTZKTBFIBJUOSLKL/
- https://security.netapp.com/advisory/ntap-20241122-0004/
- https://access.redhat.com/errata/RHSA-2024:2463
- https://access.redhat.com/errata/RHSA-2024:3203
- https://access.redhat.com/security/cve/CVE-2023-7008
- https://bugzilla.redhat.com/show_bug.cgi?id=2222261
- https://bugzilla.redhat.com/show_bug.cgi?id=2222672
- https://github.com/systemd/systemd/issues/25676
- https://lists.debian.org/debian-lts-announce/2024/09/msg00001.html
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU Binutils before 2.40 was discovered to contain an excessive memory consumption vulnerability via the function bfd_dwarf2_find_nearest_line_with_alt at dwarf2.c. The attacker could supply a crafted ELF file and cause a DNS attack.
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-48064
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=8f2c64de86bc3d7556121fe296dd679000283931
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/3XKYUAIORNQ32IZUOZFURECZKEXOHX7Z/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NSUNHSOWWLLNGHRM5TUBNCJHEYHPDX2M/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/KGSKF4GH7425S6XFDQMWTJGD5U47BAZN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/3XKYUAIORNQ32IZUOZFURECZKEXOHX7Z/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/KGSKF4GH7425S6XFDQMWTJGD5U47BAZN/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/NSUNHSOWWLLNGHRM5TUBNCJHEYHPDX2M/
- https://security.netapp.com/advisory/ntap-20231006-0008/
- https://sourceware.org/bugzilla/show_bug.cgi?id=29922
- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git%3Bh=8f2c64de86bc3d7556121fe296dd679000283931
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GNU binutils gold gold v1.11-v1.16 (GNU binutils v2.21-v2.31.1) is affected by: Improper Input Validation, Signed/Unsigned Comparison, Out-of-bounds Read. The impact is: Denial of service. The component is: gold/fileread.cc:497, elfcpp/elfcpp_file.h:644. The attack vector is: An ELF file with an invalid e_shoff header field must be opened.
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-1010204
- https://support.f5.com/csp/article/K05032915?utm_source=f5support&utm_medium=RSS
- https://security-tracker.debian.org/tracker/CVE-2019-1010204
- https://sourceware.org/bugzilla/show_bug.cgi?id=23765
- https://security.netapp.com/advisory/ntap-20190822-0001/
- https://support.f5.com/csp/article/K05032915?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-27538
- https://curl.se/docs/CVE-2023-27538.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/36NBD5YLJXXEDZLDGNFCERWRYJQ6LAQW/
- https://hackerone.com/reports/1898475
- https://lists.debian.org/debian-lts-announce/2023/04/msg00025.html
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230420-0010/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.21
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Processing a maliciously formatted PKCS12 file may lead OpenSSL to crash leading to a potential Denial of Service attack
Impact summary: Applications loading files in the PKCS12 format from untrusted sources might terminate abruptly.
A file in PKCS12 format can contain certificates and keys and may come from an untrusted source. The PKCS12 specification allows certain fields to be NULL, but OpenSSL does not correctly check for this case. This can lead to a NULL pointer dereference that results in OpenSSL crashing. If an application processes PKCS12 files from an untrusted source using the OpenSSL APIs then that application will be vulnerable to this issue.
OpenSSL APIs that are vulnerable to this are: PKCS12_parse(), PKCS12_unpack_p7data(), PKCS12_unpack_p7encdata(), PKCS12_unpack_authsafes() and PKCS12_newpass().
We have also fixed a similar issue in SMIME_write_PKCS7(). However since this function is related to writing data we do not consider it security significant.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.21 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-0727
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20240208-0006/
- https://github.com/openssl/openssl/commit/09df4395b5071217b76dc7d3d2e630eb8c5a79c2
- https://github.com/openssl/openssl/commit/775acfdbd0c6af9ac855f34969cdab0c0c90844a
- https://github.com/openssl/openssl/commit/d135eeab8a5dbf72b3da5240bab9ddb7678dbd2c
- https://github.openssl.org/openssl/extended-releases/commit/03b3941d60c4bce58fab69a0c22377ab439bc0e8
- https://github.openssl.org/openssl/extended-releases/commit/aebaa5883e31122b404e450732dc833dc9dee539
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://www.openssl.org/news/secadv/20240125.txt
low severity
- Vulnerable module: patch
- Introduced through: patch@2.7.6-6
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › patch@2.7.6-6
NVD Description
Note: Versions mentioned in the description apply only to the upstream patch package and not the patch package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An Invalid Pointer vulnerability exists in GNU patch 2.7 via the another_hunk function, which causes a Denial of Service.
Remediation
There is no fixed version for Ubuntu:20.04 patch.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.4 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
- Fixed in: 1:4.8.1-1ubuntu5.20.04.5
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/login@1:4.8.1-1ubuntu5.20.04.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.
Remediation
Upgrade Ubuntu:20.04 shadow to version 1:4.8.1-1ubuntu5.20.04.5 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-4641
- https://access.redhat.com/errata/RHSA-2023:6632
- https://access.redhat.com/errata/RHSA-2023:7112
- https://access.redhat.com/errata/RHSA-2024:0417
- https://access.redhat.com/errata/RHSA-2024:2577
- https://access.redhat.com/security/cve/CVE-2023-4641
- https://bugzilla.redhat.com/show_bug.cgi?id=2215945
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.20
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Checking excessively long DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The function DH_check() performs various checks on DH parameters. After fixing CVE-2023-3446 it was discovered that a large q parameter value can also trigger an overly long computation during some of these checks. A correct q value, if present, cannot be larger than the modulus p parameter, thus it is unnecessary to perform these checks if q is larger than p.
An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the "-check" option.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.20 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-3817
- http://seclists.org/fulldisclosure/2023/Jul/43
- http://www.openwall.com/lists/oss-security/2023/07/31/1
- http://www.openwall.com/lists/oss-security/2023/09/22/11
- http://www.openwall.com/lists/oss-security/2023/09/22/9
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230818-0014/
- https://security.netapp.com/advisory/ntap-20231027-0008/
- https://security.netapp.com/advisory/ntap-20240621-0006/
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=6a1eb62c29db6cb5eec707f9338aee00f44e26f5
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=869ad69aadd985c7b8ca6f4e5dd0eb274c9f3644
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9002fd07327a91f35ba6c1307e71fa6fd4409b7f
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=91ddeba0f2269b017dc06c46c993a788974b1aa5
- https://www.openssl.org/news/secadv/20230731.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
The function X509_VERIFY_PARAM_add0_policy() is documented to implicitly enable the certificate policy check when doing certificate verification. However the implementation of the function does not enable the check which allows certificates with invalid or incorrect policies to pass the certificate verification.
As suddenly enabling the policy check could break existing deployments it was decided to keep the existing behavior of the X509_VERIFY_PARAM_add0_policy() function.
Instead the applications that require OpenSSL to perform certificate policy check need to use X509_VERIFY_PARAM_set1_policies() or explicitly enable the policy check by calling X509_VERIFY_PARAM_set_flags() with the X509_V_FLAG_POLICY_CHECK flag argument.
Certificate policy checks are disabled by default in OpenSSL and are not commonly used by applications.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-0466
- http://www.openwall.com/lists/oss-security/2023/09/28/4
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=0d16b7e99aafc0b4a6d729eec65a411a7e025f0a
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=51e8a84ce742db0f6c70510d0159dad8f7825908
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=73398dea26de9899fb4baa94098ad0a61f435c72
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fc814a30fc4f0bc54fcea7d9a7462f5457aab061
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230414-0001/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230328.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.18
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Applications that use a non-default option when verifying certificates may be vulnerable to an attack from a malicious CA to circumvent certain checks.
Invalid certificate policies in leaf certificates are silently ignored by OpenSSL and other certificate policy checks are skipped for that certificate. A malicious CA could use this to deliberately assert invalid certificate policies in order to circumvent policy checking on the certificate altogether.
Policy processing is disabled by default but can be enabled by passing
the -policy' argument to the command line utilities or by calling the X509_VERIFY_PARAM_set1_policies()' function.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.18 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-0465
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=10325176f3d3e98c6e2b3bf5ab1e3b334de6947a
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=1dd43e0709fece299b15208f36cc7c76209ba0bb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=b013765abfa80036dc779dd0e50602c57bb3bf95
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=facfb1ab745646e97a1920977ae4a9965ea61d5c
- https://lists.debian.org/debian-lts-announce/2023/06/msg00011.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230414-0001/
- https://www.debian.org/security/2023/dsa-5417
- https://www.openssl.org/news/secadv/20230328.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.21
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Generating excessively long X9.42 DH keys or checking excessively long X9.42 DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_generate_key() to generate an X9.42 DH key may experience long delays. Likewise, applications that use DH_check_pub_key(), DH_check_pub_key_ex() or EVP_PKEY_public_check() to check an X9.42 DH key or X9.42 DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
While DH_check() performs all the necessary checks (as of CVE-2023-3817), DH_check_pub_key() doesn't make any of these checks, and is therefore vulnerable for excessively large P and Q parameters.
Likewise, while DH_generate_key() performs a check for an excessively large P, it doesn't check for an excessively large Q.
An application that calls DH_generate_key() or DH_check_pub_key() and supplies a key or parameters obtained from an untrusted source could be vulnerable to a Denial of Service attack.
DH_generate_key() and DH_check_pub_key() are also called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_pub_key_ex(), EVP_PKEY_public_check(), and EVP_PKEY_generate().
Also vulnerable are the OpenSSL pkey command line application when using the "-pubcheck" option, as well as the OpenSSL genpkey command line application.
The OpenSSL SSL/TLS implementation is not affected by this issue.
The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.21 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-5678
- http://www.openwall.com/lists/oss-security/2023/11/06/2
- http://www.openwall.com/lists/oss-security/2024/03/11/1
- https://security.netapp.com/advisory/ntap-20231130-0010/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=34efaef6c103d636ab507a0cc34dca4d3aecc055
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=710fee740904b6290fef0dd5536fbcedbc38ff0c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=db925ae2e65d0d925adef429afc37f75bd1c2017
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ddeb4b6c6d527e54ce9a99cba785c0f7776e54b6
- https://www.openssl.org/news/secadv/20231106.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.20
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Checking excessively long DH keys or parameters may be very slow.
Impact summary: Applications that use the functions DH_check(), DH_check_ex() or EVP_PKEY_param_check() to check a DH key or DH parameters may experience long delays. Where the key or parameters that are being checked have been obtained from an untrusted source this may lead to a Denial of Service.
The function DH_check() performs various checks on DH parameters. One of those checks confirms that the modulus ('p' parameter) is not too large. Trying to use a very large modulus is slow and OpenSSL will not normally use a modulus which is over 10,000 bits in length.
However the DH_check() function checks numerous aspects of the key or parameters that have been supplied. Some of those checks use the supplied modulus value even if it has already been found to be too large.
An application that calls DH_check() and supplies a key or parameters obtained from an untrusted source could be vulernable to a Denial of Service attack.
The function DH_check() is itself called by a number of other OpenSSL functions. An application calling any of those other functions may similarly be affected. The other functions affected by this are DH_check_ex() and EVP_PKEY_param_check().
Also vulnerable are the OpenSSL dhparam and pkeyparam command line applications when using the '-check' option.
The OpenSSL SSL/TLS implementation is not affected by this issue. The OpenSSL 3.0 and 3.1 FIPS providers are not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.20 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-3446
- http://www.openwall.com/lists/oss-security/2023/07/19/4
- http://www.openwall.com/lists/oss-security/2023/07/19/5
- http://www.openwall.com/lists/oss-security/2023/07/19/6
- http://www.openwall.com/lists/oss-security/2023/07/31/1
- http://www.openwall.com/lists/oss-security/2024/05/16/1
- https://lists.debian.org/debian-lts-announce/2023/08/msg00019.html
- https://security.gentoo.org/glsa/202402-08
- https://security.netapp.com/advisory/ntap-20230803-0011/
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=1fa20cf2f506113c761777127a38bce5068740eb
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=8780a896543a654e757db1b9396383f9d8095528
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=9a0a4d3c1e7138915563c0df4fe6a3f9377b839c
- https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=fc9867c1e03c22ebf56943be205202e576aabf23
- https://www.openssl.org/news/secadv/20230719.txt
low severity
- Vulnerable module: gcc-10/gcc-10-base
- Introduced through: gcc-10/gcc-10-base@10.3.0-1ubuntu1~20.04, gcc-10/libgcc-s1@10.3.0-1ubuntu1~20.04 and others
- Fixed in: 10.5.0-1ubuntu1~20.04.1+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gcc-10/gcc-10-base@10.3.0-1ubuntu1~20.04
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gcc-10/libgcc-s1@10.3.0-1ubuntu1~20.04
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gcc-10/libstdc++6@10.3.0-1ubuntu1~20.04
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-10 package and not the gcc-10 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.
The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
Remediation
Upgrade Ubuntu:20.04 gcc-10 to version 10.5.0-1ubuntu1~20.04.1+esm1 or higher.
References
low severity
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in libssh, a library that implements the SSH protocol. When calculating the session ID during the key exchange (KEX) process, an allocation failure in cryptographic functions may lead to a NULL pointer dereference. This issue can cause the client or server to crash.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-8114
- https://access.redhat.com/security/cve/CVE-2025-8114
- https://bugzilla.redhat.com/show_bug.cgi?id=2383220
- https://git.libssh.org/projects/libssh.git/commit/?id=53ac23ded4cb2c5463f6c4cd1525331bd578812d
- https://www.libssh.org/security/advisories/CVE-2025-8114.txt
- https://git.libssh.org/projects/libssh.git/commit/?id=65f363c9
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.4 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/login@1:4.8.1-1ubuntu5.20.04.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees
Remediation
There is no fixed version for Ubuntu:20.04 shadow.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2013-4235
- https://security-tracker.debian.org/tracker/CVE-2013-4235
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-4235
- https://access.redhat.com/security/cve/cve-2013-4235
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
- https://security.gentoo.org/glsa/202210-26
low severity
- Vulnerable module: binutils
- Introduced through: binutils@2.34-6ubuntu1.4, binutils/binutils-common@2.34-6ubuntu1.4 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-common@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/binutils-x86-64-linux-gnu@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libbinutils@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf-nobfd0@2.34-6ubuntu1.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › binutils/libctf0@2.34-6ubuntu1.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream binutils package and not the binutils package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."
Remediation
There is no fixed version for Ubuntu:20.04 binutils.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.19
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (CURLOPT_READFUNCTION) to ask for data to send, even when the CURLOPT_POSTFIELDS option has been set, if the same handle previously wasused to issue a PUT request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.19 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-28322
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- http://seclists.org/fulldisclosure/2023/Jul/47
- http://seclists.org/fulldisclosure/2023/Jul/48
- http://seclists.org/fulldisclosure/2023/Jul/52
- https://hackerone.com/reports/1954658
- https://lists.debian.org/debian-lts-announce/2023/12/msg00015.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/F4I75RDGX5ULSSCBE5BF3P5I5SFO7ULQ/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Z2LIWHWKOVH24COGGBCVOWDXXIUPKOMK/
- https://security.gentoo.org/glsa/202310-12
- https://security.netapp.com/advisory/ntap-20230609-0009/
- https://support.apple.com/kb/HT213843
- https://support.apple.com/kb/HT213844
- https://support.apple.com/kb/HT213845
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.20
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met.
libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers.
libcurl provides a function call that duplicates en easy handle called curl_easy_duphandle.
If a transfer has cookies enabled when the handle is duplicated, the
cookie-enable state is also cloned - but without cloning the actual
cookies. If the source handle did not read any cookies from a specific file on
disk, the cloned version of the handle would instead store the file name as
none (using the four ASCII letters, no quotes).
Subsequent use of the cloned handle that does not explicitly set a source to
load cookies from would then inadvertently load cookies from a file named
none - if such a file exists and is readable in the current directory of the
program using libcurl. And if using the correct file format of course.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.20 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-38546
- http://seclists.org/fulldisclosure/2024/Jan/34
- http://seclists.org/fulldisclosure/2024/Jan/37
- http://seclists.org/fulldisclosure/2024/Jan/38
- https://curl.se/docs/CVE-2023-38546.html
- https://forum.vmssoftware.com/viewtopic.php?f=8&t=8868
- https://lists.debian.org/debian-lts-announce/2023/10/msg00016.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/OGMXNRNSJ4ETDK6FRNU3J7SABXPWCHSQ/
- https://support.apple.com/kb/HT214036
- https://support.apple.com/kb/HT214057
- https://support.apple.com/kb/HT214058
- https://support.apple.com/kb/HT214063
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.19-3ubuntu2.2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › gnupg2/gpgv@2.2.19-3ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Remediation
There is no fixed version for Ubuntu:20.04 gnupg2.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-3219
- https://access.redhat.com/security/cve/CVE-2022-3219
- https://bugzilla.redhat.com/show_bug.cgi?id=2127010
- https://dev.gnupg.org/D556
- https://dev.gnupg.org/T5993
- https://marc.info/?l=oss-security&m=165696590211434&w=4
- https://security.netapp.com/advisory/ntap-20230324-0001/
low severity
- Vulnerable module: procps
- Introduced through: procps@2:3.3.16-1ubuntu2.3 and procps/libprocps8@2:3.3.16-1ubuntu2.3
- Fixed in: 2:3.3.16-1ubuntu2.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › procps@2:3.3.16-1ubuntu2.3
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › procps/libprocps8@2:3.3.16-1ubuntu2.3
NVD Description
Note: Versions mentioned in the description apply only to the upstream procps package and not the procps package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Under some circumstances, this weakness allows a user who has access to run the “ps” utility on a machine, the ability to write almost unlimited amounts of unfiltered data into the process heap.
Remediation
Upgrade Ubuntu:20.04 procps to version 2:3.3.16-1ubuntu2.4 or higher.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.4 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/login@1:4.8.1-1ubuntu5.20.04.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.
Remediation
There is no fixed version for Ubuntu:20.04 shadow.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2023-29383
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
- https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2023-29383-abusing-linux-chfn-to-misrepresent-etc-passwd/
- https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=31797
low severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libssh package and not the libssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A flaw was found in libssh's handling of key exchange (KEX) processes when a client repeatedly sends incorrect KEX guesses. The library fails to free memory during these rekey operations, which can gradually exhaust system memory. This issue can lead to crashes on the client side, particularly when using libgcrypt, which impacts application stability and availability.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm3 or higher.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.25
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When asked to both use a .netrc file for credentials and to follow HTTP
redirects, curl could leak the password used for the first host to the
followed-to host under certain circumstances.
This flaw only manifests itself if the netrc file has an entry that matches the redirect target hostname but the entry either omits just the password or omits both login and password.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.25 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-11053
- https://curl.se/docs/CVE-2024-11053.html
- https://curl.se/docs/CVE-2024-11053.json
- https://hackerone.com/reports/2829063
- http://www.openwall.com/lists/oss-security/2024/12/11/1
- https://security.netapp.com/advisory/ntap-20250124-0012/
- https://security.netapp.com/advisory/ntap-20250131-0003/
- https://security.netapp.com/advisory/ntap-20250131-0004/
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.25+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.25+esm2 or higher.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
- Fixed in: 7.68.0-1ubuntu2.25+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.
Remediation
Upgrade Ubuntu:20.04 curl to version 7.68.0-1ubuntu2.25+esm2 or higher.
References
low severity
new
- Vulnerable module: curl
- Introduced through: curl@7.68.0-1ubuntu2.15, curl/libcurl3-gnutls@7.68.0-1ubuntu2.15 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl3-gnutls@7.68.0-1ubuntu2.15
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › curl/libcurl4@7.68.0-1ubuntu2.15
NVD Description
Note: Versions mentioned in the description apply only to the upstream curl package and not the curl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.
Remediation
There is no fixed version for Ubuntu:20.04 curl.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.9 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.2, krb5/libk5crypto3@1.17-6ubuntu4.2 and others
- Fixed in: 1.17-6ubuntu4.9
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libgssapi-krb5-2@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libk5crypto3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5-3@1.17-6ubuntu4.2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › krb5/libkrb5support0@1.17-6ubuntu4.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream krb5 package and not the krb5 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
Remediation
Upgrade Ubuntu:20.04 krb5 to version 1.17-6ubuntu4.9 or higher.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.8.5-5ubuntu1.1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libgcrypt20@1.8.5-5ubuntu1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
Remediation
There is no fixed version for Ubuntu:20.04 libgcrypt20.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-2236
- https://access.redhat.com/errata/RHSA-2024:9404
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://access.redhat.com/errata/RHSA-2025:3534
- https://access.redhat.com/errata/RHSA-2025:3530
- https://access.redhat.com/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218
low severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm3 or higher.
References
low severity
new
- Vulnerable module: libssh/libssh-4
- Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.2
- Fixed in: 0.9.3-2ubuntu2.5+esm3
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › libssh/libssh-4@0.9.3-2ubuntu2.2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
Upgrade Ubuntu:20.04 libssh to version 0.9.3-2ubuntu2.5+esm3 or higher.
References
low severity
- Vulnerable module: ncurses/libncurses6
- Introduced through: ncurses/libncurses6@6.2-0ubuntu2, ncurses/libncursesw6@6.2-0ubuntu2 and others
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncurses6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libncursesw6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/libtinfo6@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-base@6.2-0ubuntu2
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › ncurses/ncurses-bin@6.2-0ubuntu2
NVD Description
Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Remediation
There is no fixed version for Ubuntu:20.04 ncurses.
References
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.13+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.)
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.13+esm1 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-61984
- https://marc.info/?l=openssh-unix-dev&m=175974522032149&w=2
- https://www.openssh.com/releasenotes.html#10.1p1
- https://www.openwall.com/lists/oss-security/2025/10/06/1
- https://dgl.cx/2025/10/bash-a-newline-ssh-proxycommand-cve-2025-61984
- http://www.openwall.com/lists/oss-security/2025/10/07/1
- http://www.openwall.com/lists/oss-security/2025/10/12/1
- https://www.vicarius.io/vsociety/posts/cve-2025-61984-detection-script-remote-code-execution-vulnerability-affecting-openssh
- https://www.vicarius.io/vsociety/posts/cve-2025-61984-mitigation-script-remote-code-execution-vulnerability-affecting-openssh
low severity
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.5
- Fixed in: 1:8.2p1-4ubuntu0.13+esm1
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssh/openssh-client@1:8.2p1-4ubuntu0.5
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssh package and not the openssh package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
ssh in OpenSSH before 10.1 allows the '\0' character in an ssh:// URI, potentially leading to code execution when a ProxyCommand is used.
Remediation
Upgrade Ubuntu:20.04 openssh to version 1:8.2p1-4ubuntu0.13+esm1 or higher.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.
Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.
There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-13176
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- https://openssl-library.org/news/secadv/20250120.txt
- http://www.openwall.com/lists/oss-security/2025/01/20/2
- https://security.netapp.com/advisory/ntap-20250124-0005/
- https://security.netapp.com/advisory/ntap-20250418-0010/
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.html
- https://security.netapp.com/advisory/ntap-20250502-0006/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.23
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Some non-default TLS server configurations can cause unbounded memory growth when processing TLSv1.3 sessions
Impact summary: An attacker may exploit certain server configurations to trigger unbounded memory growth that would lead to a Denial of Service
This problem can occur in TLSv1.3 if the non-default SSL_OP_NO_TICKET option is being used (but not if early_data support is also configured and the default anti-replay protection is in use). In this case, under certain conditions, the session cache can get into an incorrect state and it will fail to flush properly as it fills. The session cache will continue to grow in an unbounded manner. A malicious client could deliberately create the scenario for this failure to force a Denial of Service. It may also happen by accident in normal operation.
This issue only affects TLS servers supporting TLSv1.3. It does not affect TLS clients.
The FIPS modules in 3.2, 3.1 and 3.0 are not affected by this issue. OpenSSL 1.0.2 is also not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.23 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-2511
- http://www.openwall.com/lists/oss-security/2024/04/08/5
- https://security.netapp.com/advisory/ntap-20240503-0013/
- https://github.com/openssl/openssl/commit/7e4d731b1c07201ad9374c1cd9ac5263bdf35bce
- https://github.com/openssl/openssl/commit/b52867a9f618bb955bed2a3ce3db4d4f97ed8e5d
- https://github.com/openssl/openssl/commit/e9d7083e241670332e0443da0f0d4ffb52829f08
- https://github.openssl.org/openssl/extended-releases/commit/5f8d25770ae6437db119dfc951e207271a326640
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://www.openssl.org/news/secadv/20240408.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.23
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause memory to be accessed that was previously freed in some situations
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code. However, only applications that directly call the SSL_free_buffers function are affected by this issue. Applications that do not call this function are not vulnerable. Our investigations indicate that this function is rarely used by applications.
The SSL_free_buffers function is used to free the internal OpenSSL buffer used when processing an incoming record from the network. The call is only expected to succeed if the buffer is not currently in use. However, two scenarios have been identified where the buffer is freed even when still in use.
The first scenario occurs where a record header has been received from the network and processed by OpenSSL, but the full record body has not yet arrived. In this case calling SSL_free_buffers will succeed even though a record has only been partially processed and the buffer is still in use.
The second scenario occurs where a full record containing application data has been received and processed by OpenSSL but the application has only read part of this data. Again a call to SSL_free_buffers will succeed even though the buffer is still in use.
While these scenarios could occur accidentally during normal operation a malicious attacker could attempt to engineer a stituation where this occurs. We are not aware of this issue being actively exploited.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.23 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-4741
- https://github.com/openssl/openssl/commit/704f725b96aa373ee45ecfb23f6abfe8be8d9177
- https://github.com/openssl/openssl/commit/b3f0eb0a295f58f16ba43ba99dad70d4ee5c437d
- https://github.com/openssl/openssl/commit/c88c3de51020c37e8706bf7a682a162593053aac
- https://github.com/openssl/openssl/commit/e5093133c35ca82874ad83697af76f4b0f7e3bd8
- https://github.openssl.org/openssl/extended-releases/commit/f7a045f3143fc6da2ee66bf52d8df04829590dd4
- https://www.openssl.org/news/secadv/20240528.txt
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20240621-0004/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.23
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.
Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.
The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).
This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.
In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.
This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.23 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-5535
- http://www.openwall.com/lists/oss-security/2024/08/15/1
- http://www.openwall.com/lists/oss-security/2024/06/27/1
- http://www.openwall.com/lists/oss-security/2024/06/28/4
- https://security.netapp.com/advisory/ntap-20240712-0005/
- https://github.com/openssl/openssl/commit/4ada436a1946cbb24db5ab4ca082b69c1bc10f37
- https://github.com/openssl/openssl/commit/99fb785a5f85315b95288921a321a935ea29a51e
- https://github.com/openssl/openssl/commit/cf6f91f6121f4db167405db2f0de410a456f260c
- https://github.com/openssl/openssl/commit/e86ac436f0bd54d4517745483e2315650fae7b2c
- https://github.openssl.org/openssl/extended-releases/commit/9947251413065a05189a63c9b7a6c1d4e224c21c
- https://github.openssl.org/openssl/extended-releases/commit/b78ec0824da857223486660177d3b1f255c65d87
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
- https://www.openssl.org/news/secadv/20240627.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.
Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2024-9143
- https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
- https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
- https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
- https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
- https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
- https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
- https://openssl-library.org/news/secadv/20241016.txt
- http://www.openwall.com/lists/oss-security/2024/10/16/1
- http://www.openwall.com/lists/oss-security/2024/10/23/1
- http://www.openwall.com/lists/oss-security/2024/10/24/1
- https://security.netapp.com/advisory/ntap-20241101-0001/
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-68160
- https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
- https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-69418
- https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
- https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
- https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
- https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
- https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-69419
- https://github.com/openssl/openssl/commit/41be0f216404f14457bbf3b9cc488dba60b49296
- https://github.com/openssl/openssl/commit/7e9cac9832e4705b91987c2474ed06a37a93cecb
- https://github.com/openssl/openssl/commit/a26a90d38edec3748566129d824e664b54bee2e2
- https://github.com/openssl/openssl/commit/cda12de3bc0e333ea8d2c6fd15001dbdaf280015
- https://github.com/openssl/openssl/commit/ff628933755075446bca8307e8417c14d164b535
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-69420
- https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9
- https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
- https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
- https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
- https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-22795
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@1.1.1f-1ubuntu2.16 and openssl/libssl1.1@1.1.1f-1ubuntu2.16
- Fixed in: 1.1.1f-1ubuntu2.24+esm2
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl@1.1.1f-1ubuntu2.16
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › openssl/libssl1.1@1.1.1f-1ubuntu2.16
NVD Description
Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Ubuntu:20.04 openssl to version 1.1.1f-1ubuntu2.24+esm2 or higher.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2026-22796
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.4 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
Detailed paths
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/login@1:4.8.1-1ubuntu5.20.04.4
-
Introduced through: maven@3.8.7-eclipse-temurin-17-focal › shadow/passwd@1:4.8.1-1ubuntu5.20.04.4
NVD Description
Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu.
See How to fix? for Ubuntu:20.04 relevant fixed versions and status.
shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.
Remediation
There is no fixed version for Ubuntu:20.04 shadow.