Vulnerabilities |
27 via 76 paths |
|---|---|
Dependencies |
167 |
Source |
Docker |
Target OS |
ubuntu:22.04 |
medium severity
- Vulnerable module: git
- Introduced through: git@1:2.34.1-1ubuntu1.15 and git/git-man@1:2.34.1-1ubuntu1.15
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › git@1:2.34.1-1ubuntu1.15
-
Introduced through: buildpack-deps@jammy-scm › git/git-man@1:2.34.1-1ubuntu1.15
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:22.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:22.04 git.
References
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.4.0-11ubuntu2.6, pam/libpam-modules-bin@1.4.0-11ubuntu2.6 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › pam/libpam-modules@1.4.0-11ubuntu2.6
-
Introduced through: buildpack-deps@jammy-scm › pam/libpam-modules-bin@1.4.0-11ubuntu2.6
-
Introduced through: buildpack-deps@jammy-scm › pam/libpam-runtime@1.4.0-11ubuntu2.6
-
Introduced through: buildpack-deps@jammy-scm › pam/libpam0g@1.4.0-11ubuntu2.6
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:22.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:22.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: wget
- Introduced through: wget@1.21.2-2ubuntu1.1
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › wget@1.21.2-2ubuntu1.1
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:22.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:22.04 wget.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › expat/libexpat1@2.4.7-1ubuntu0.7
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:22.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:22.04 expat.
References
medium severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.27-3ubuntu2.5, gnupg2/gnupg@2.2.27-3ubuntu2.5 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/dirmngr@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gnupg@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gnupg-l10n@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gnupg-utils@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg-agent@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpgconf@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpgsm@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpgv@2.2.27-3ubuntu2.5
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:22.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:22.04 gnupg2.
References
medium severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1ubuntu0.1.22.04.2
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › tar@1.34+dfsg-1ubuntu0.1.22.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:22.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:22.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
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.35-0ubuntu3.13 and glibc/libc6@2.35-0ubuntu3.13
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › glibc/libc-bin@2.35-0ubuntu3.13
-
Introduced through: buildpack-deps@jammy-scm › glibc/libc6@2.35-0ubuntu3.13
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:22.04 relevant fixed versions and status.
sha256crypt and sha512crypt through 0.6 allow attackers to cause a denial of service (CPU consumption) because the algorithm's runtime is proportional to the square of the length of the password.
Remediation
There is no fixed version for Ubuntu:22.04 glibc.
References
low severity
- Vulnerable module: libzstd/libzstd1
- Introduced through: libzstd/libzstd1@1.4.8+dfsg-3build1
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › libzstd/libzstd1@1.4.8+dfsg-3build1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libzstd package and not the libzstd package as distributed by Ubuntu.
See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
A vulnerability was found in zstd v1.4.10, where an attacker can supply empty string as an argument to the command line tool to cause buffer overrun.
Remediation
There is no fixed version for Ubuntu:22.04 libzstd.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-4899
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/C63HAGVLQA6FJNDCHR7CNZZL6VSLILB2/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/JEHRBBYYTPA4DETOM5XAKGCP37NUTLOA/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QYLDK6ODVC4LJSDULLX6Q2YHTFOWABCN/
- https://github.com/facebook/zstd/issues/3200
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/C63HAGVLQA6FJNDCHR7CNZZL6VSLILB2/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JEHRBBYYTPA4DETOM5XAKGCP37NUTLOA/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/QYLDK6ODVC4LJSDULLX6Q2YHTFOWABCN/
- https://security.netapp.com/advisory/ntap-20230725-0005/
low severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.39-3ubuntu0.1
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › pcre2/libpcre2-8-0@10.39-3ubuntu0.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:22.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:22.04 pcre2.
References
low severity
- Vulnerable module: pcre3/libpcre3
- Introduced through: pcre3/libpcre3@2:8.39-13ubuntu0.22.04.1
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › pcre3/libpcre3@2:8.39-13ubuntu0.22.04.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:22.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:22.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: coreutils
- Introduced through: coreutils@8.32-4.1ubuntu1.2
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › coreutils@8.32-4.1ubuntu1.2
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:22.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:22.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.3-2ubuntu0.1, ncurses/libncursesw6@6.3-2ubuntu0.1 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › ncurses/libncurses6@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/libncursesw6@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/libtinfo6@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/ncurses-base@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/ncurses-bin@6.3-2ubuntu0.1
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:22.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:22.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: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@249.11-0ubuntu3.17 and systemd/libudev1@249.11-0ubuntu3.17
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › systemd/libsystemd0@249.11-0ubuntu3.17
-
Introduced through: buildpack-deps@jammy-scm › systemd/libudev1@249.11-0ubuntu3.17
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:22.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:22.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: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.3.0-1ubuntu1~22.04.2, gcc-12/libgcc-s1@12.3.0-1ubuntu1~22.04.2 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › gcc-12/gcc-12-base@12.3.0-1ubuntu1~22.04.2
-
Introduced through: buildpack-deps@jammy-scm › gcc-12/libgcc-s1@12.3.0-1ubuntu1~22.04.2
-
Introduced through: buildpack-deps@jammy-scm › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Ubuntu.
See How to fix? for Ubuntu:22.04 relevant fixed versions and status.
libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.
Remediation
There is no fixed version for Ubuntu:22.04 gcc-12.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2022-27943
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
- https://sourceware.org/bugzilla/show_bug.cgi?id=28995
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
low severity
- Vulnerable module: gnupg2/dirmngr
- Introduced through: gnupg2/dirmngr@2.2.27-3ubuntu2.5, gnupg2/gnupg@2.2.27-3ubuntu2.5 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/dirmngr@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gnupg@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gnupg-l10n@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gnupg-utils@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg-agent@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg-wks-client@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpg-wks-server@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpgconf@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpgsm@2.2.27-3ubuntu2.5
-
Introduced through: buildpack-deps@jammy-scm › gnupg2/gpgv@2.2.27-3ubuntu2.5
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:22.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:22.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: shadow/login
- Introduced through: shadow/login@1:4.8.1-2ubuntu2.2 and shadow/passwd@1:4.8.1-2ubuntu2.2
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › shadow/login@1:4.8.1-2ubuntu2.2
-
Introduced through: buildpack-deps@jammy-scm › shadow/passwd@1:4.8.1-2ubuntu2.2
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:22.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:22.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
- Vulnerable module: curl
- Introduced through: curl@7.81.0-1ubuntu1.21, curl/libcurl3-gnutls@7.81.0-1ubuntu1.21 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › curl@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl3-gnutls@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl4@7.81.0-1ubuntu1.21
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:22.04 relevant fixed versions and status.
When asked to 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 a default entry that
omits both login and password. A rare circumstance.
Remediation
There is no fixed version for Ubuntu:22.04 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.81.0-1ubuntu1.21, curl/libcurl3-gnutls@7.81.0-1ubuntu1.21 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › curl@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl3-gnutls@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl4@7.81.0-1ubuntu1.21
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:22.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
There is no fixed version for Ubuntu:22.04 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.81.0-1ubuntu1.21, curl/libcurl3-gnutls@7.81.0-1ubuntu1.21 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › curl@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl3-gnutls@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl4@7.81.0-1ubuntu1.21
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:22.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
There is no fixed version for Ubuntu:22.04 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.81.0-1ubuntu1.21, curl/libcurl3-gnutls@7.81.0-1ubuntu1.21 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › curl@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl3-gnutls@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl4@7.81.0-1ubuntu1.21
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:22.04 relevant fixed versions and status.
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
Remediation
There is no fixed version for Ubuntu:22.04 curl.
References
low severity
- Vulnerable module: curl
- Introduced through: curl@7.81.0-1ubuntu1.21, curl/libcurl3-gnutls@7.81.0-1ubuntu1.21 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › curl@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl3-gnutls@7.81.0-1ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › curl/libcurl4@7.81.0-1ubuntu1.21
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:22.04 relevant fixed versions and status.
- A cookie is set using the
securekeyword forhttps://target - curl is redirected to or otherwise made to speak with
http://target(same hostname, but using clear text HTTP) using the same cookie set - The same cookie name is set - but with just a slash as path (
path=\"/\",). Since this site is not secure, the cookie should just be ignored. - A bug in the path comparison logic makes curl read outside a heap buffer boundary
The bug either causes a crash or it potentially makes the comparison come to the wrong conclusion and lets the clear-text site override the contents of the secure cookie, contrary to expectations and depending on the memory contents immediately following the single-byte allocation that holds the path.
The presumed and correct behavior would be to plainly ignore the second set of the cookie since it was already set as secure on a secure host so overriding it on an insecure host should not be okay.
Remediation
There is no fixed version for Ubuntu:22.04 curl.
References
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2025-9086
- https://curl.se/docs/CVE-2025-9086.html
- https://curl.se/docs/CVE-2025-9086.json
- https://hackerone.com/reports/3294999
- http://www.openwall.com/lists/oss-security/2025/09/10/1
- https://lists.debian.org/debian-lts-announce/2026/01/msg00002.html
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.9.4-3ubuntu3
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › libgcrypt20@1.9.4-3ubuntu3
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:22.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:22.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
- Vulnerable module: ncurses/libncurses6
- Introduced through: ncurses/libncurses6@6.3-2ubuntu0.1, ncurses/libncursesw6@6.3-2ubuntu0.1 and others
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › ncurses/libncurses6@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/libncursesw6@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/libtinfo6@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/ncurses-base@6.3-2ubuntu0.1
-
Introduced through: buildpack-deps@jammy-scm › ncurses/ncurses-bin@6.3-2ubuntu0.1
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:22.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:22.04 ncurses.
References
low severity
new
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.9p1-3ubuntu0.13
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › openssh/openssh-client@1:8.9p1-3ubuntu0.13
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:22.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
There is no fixed version for Ubuntu:22.04 openssh.
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
new
- Vulnerable module: openssh/openssh-client
- Introduced through: openssh/openssh-client@1:8.9p1-3ubuntu0.13
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › openssh/openssh-client@1:8.9p1-3ubuntu0.13
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:22.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
There is no fixed version for Ubuntu:22.04 openssh.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.2-0ubuntu1.21 and openssl/libssl3@3.0.2-0ubuntu1.21
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › openssl@3.0.2-0ubuntu1.21
-
Introduced through: buildpack-deps@jammy-scm › openssl/libssl3@3.0.2-0ubuntu1.21
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:22.04 relevant fixed versions and status.
Validating the order of the public keys in the Diffie-Hellman Key Agreement Protocol, when an approved safe prime is used, allows remote attackers (from the client side) to trigger unnecessarily expensive server-side DHE modular-exponentiation calculations. The client may cause asymmetric resource consumption. The basic attack scenario is that the client must claim that it can only communicate with DHE, and the server must be configured to allow DHE and validate the order of the public key.
Remediation
There is no fixed version for Ubuntu:22.04 openssl.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.8.1-2ubuntu2.2 and shadow/passwd@1:4.8.1-2ubuntu2.2
Detailed paths
-
Introduced through: buildpack-deps@jammy-scm › shadow/login@1:4.8.1-2ubuntu2.2
-
Introduced through: buildpack-deps@jammy-scm › shadow/passwd@1:4.8.1-2ubuntu2.2
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:22.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:22.04 shadow.