Vulnerabilities

30 via 88 paths

Dependencies

146

Source

Group 6 Copy Created with Sketch. Docker

Target OS

ubuntu:24.04
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 12
  • 18
Status
  • 30
  • 0
  • 0

medium severity

Directory Traversal

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.5.3-5ubuntu5.5, pam/libpam-modules-bin@1.5.3-5ubuntu5.5 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 pam/libpam-modules@1.5.3-5ubuntu5.5
  • Introduced through: tomcat@10-jdk17 pam/libpam-modules-bin@1.5.3-5ubuntu5.5
  • Introduced through: tomcat@10-jdk17 pam/libpam-runtime@1.5.3-5ubuntu5.5
  • Introduced through: tomcat@10-jdk17 pam/libpam0g@1.5.3-5ubuntu5.5

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:24.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:24.04 pam.

References

medium severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.21.4-1ubuntu4.1

Detailed paths

  • Introduced through: tomcat@10-jdk17 wget@1.21.4-1ubuntu4.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:24.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:24.04 wget.

References

medium severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.42-4ubuntu2.8, binutils/binutils-common@2.42-4ubuntu2.8 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 binutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-common@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-x86-64-linux-gnu@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libbinutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf-nobfd0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libgprofng0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libsframe1@2.42-4ubuntu2.8

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:24.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:24.04 binutils.

References

medium severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.6.1-2ubuntu0.4

Detailed paths

  • Introduced through: tomcat@10-jdk17 expat/libexpat1@2.6.1-2ubuntu0.4

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:24.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:24.04 expat.

References

medium severity
new

Algorithmic Complexity

  • Vulnerable module: gnutls28/libgnutls30t64
  • Introduced through: gnutls28/libgnutls30t64@3.8.3-1.1ubuntu3.4
  • Fixed in: 3.8.3-1.1ubuntu3.5

Detailed paths

  • Introduced through: tomcat@10-jdk17 gnutls28/libgnutls30t64@3.8.3-1.1ubuntu3.4

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:24.04 relevant fixed versions and status.

A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).

Remediation

Upgrade Ubuntu:24.04 gnutls28 to version 3.8.3-1.1ubuntu3.5 or higher.

References

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.4.4-2ubuntu17.4, gnupg2/gnupg@2.4.4-2ubuntu17.4 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 gnupg2/dirmngr@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gnupg@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gnupg-utils@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpg@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpg-agent@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpgsm@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpgv@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/keyboxd@2.4.4-2ubuntu17.4

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:24.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:24.04 gnupg2.

References

medium severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.42-4ubuntu2.8, binutils/binutils-common@2.42-4ubuntu2.8 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 binutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-common@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-x86-64-linux-gnu@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libbinutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf-nobfd0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libgprofng0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libsframe1@2.42-4ubuntu2.8

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:24.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:24.04 binutils.

References

medium severity
new

CVE-2025-14017

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6
  • Fixed in: 8.5.0-2ubuntu10.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.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:24.04 curl to version 8.5.0-2ubuntu10.7 or higher.

References

medium severity
new

CVE-2026-0964

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.10.6-2ubuntu0.2
  • Fixed in: 0.10.6-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@10-jdk17 libssh/libssh-4@0.10.6-2ubuntu0.2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Ubuntu:24.04 libssh to version 0.10.6-2ubuntu0.3 or higher.

References

medium severity
new

CVE-2026-0967

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.10.6-2ubuntu0.2
  • Fixed in: 0.10.6-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@10-jdk17 libssh/libssh-4@0.10.6-2ubuntu0.2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Ubuntu:24.04 libssh to version 0.10.6-2ubuntu0.3 or higher.

References

medium severity
new

CVE-2026-0968

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.10.6-2ubuntu0.2
  • Fixed in: 0.10.6-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@10-jdk17 libssh/libssh-4@0.10.6-2ubuntu0.2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Ubuntu:24.04 libssh to version 0.10.6-2ubuntu0.3 or higher.

References

medium severity

Directory Traversal

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3build1

Detailed paths

  • Introduced through: tomcat@10-jdk17 tar@1.35+dfsg-3build1

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:24.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:24.04 tar.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.39-0ubuntu8.7, glibc/libc6@2.39-0ubuntu8.7 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 glibc/libc-bin@2.39-0ubuntu8.7
  • Introduced through: tomcat@10-jdk17 glibc/libc6@2.39-0ubuntu8.7
  • Introduced through: tomcat@10-jdk17 glibc/locales@2.39-0ubuntu8.7

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:24.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:24.04 glibc.

References

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.4-3ubuntu6.1

Detailed paths

  • Introduced through: tomcat@10-jdk17 coreutils@9.4-3ubuntu6.1

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:24.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:24.04 coreutils.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.42-4ubuntu2.8, binutils/binutils-common@2.42-4ubuntu2.8 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 binutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-common@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-x86-64-linux-gnu@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libbinutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf-nobfd0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libgprofng0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libsframe1@2.42-4ubuntu2.8

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:24.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:24.04 binutils.

References

low severity
new

Stack-based Buffer Overflow

  • Vulnerable module: gnutls28/libgnutls30t64
  • Introduced through: gnutls28/libgnutls30t64@3.8.3-1.1ubuntu3.4
  • Fixed in: 3.8.3-1.1ubuntu3.5

Detailed paths

  • Introduced through: tomcat@10-jdk17 gnutls28/libgnutls30t64@3.8.3-1.1ubuntu3.4

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:24.04 relevant fixed versions and status.

A flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.

Remediation

Upgrade Ubuntu:24.04 gnutls28 to version 3.8.3-1.1ubuntu3.5 or higher.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.42-4ubuntu2.8, binutils/binutils-common@2.42-4ubuntu2.8 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 binutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-common@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/binutils-x86-64-linux-gnu@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libbinutils@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf-nobfd0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libctf0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libgprofng0@2.42-4ubuntu2.8
  • Introduced through: tomcat@10-jdk17 binutils/libsframe1@2.42-4ubuntu2.8

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:24.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:24.04 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.4.4-2ubuntu17.4, gnupg2/gnupg@2.4.4-2ubuntu17.4 and others

Detailed paths

  • Introduced through: tomcat@10-jdk17 gnupg2/dirmngr@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gnupg@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gnupg-utils@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpg@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpg-agent@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpgconf@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpgsm@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/gpgv@2.4.4-2ubuntu17.4
  • Introduced through: tomcat@10-jdk17 gnupg2/keyboxd@2.4.4-2ubuntu17.4

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:24.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:24.04 gnupg2.

References

low severity
new

Memory Leak

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.10.6-2ubuntu0.2
  • Fixed in: 0.10.6-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@10-jdk17 libssh/libssh-4@0.10.6-2ubuntu0.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:24.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:24.04 libssh to version 0.10.6-2ubuntu0.3 or higher.

References

low severity

CVE-2025-0167

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.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:24.04 curl.

References

low severity

CVE-2025-10148

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6
  • Fixed in: 8.5.0-2ubuntu10.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.04 relevant fixed versions and status.

curl's websocket code did not update the 32 bit mask pattern for each new outgoing frame as the specification says. Instead it used a fixed mask that persisted and was used throughout the entire connection.

A predictable mask pattern allows for a malicious server to induce traffic between the two communicating parties that could be interpreted by an involved proxy (configured or transparent) as genuine, real, HTTP traffic with content and thereby poison its cache. That cached poisoned content could then be served to all users of that proxy.

Remediation

Upgrade Ubuntu:24.04 curl to version 8.5.0-2ubuntu10.7 or higher.

References

low severity

CVE-2025-14819

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6
  • Fixed in: 8.5.0-2ubuntu10.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.04 relevant fixed versions and status.

When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.

Remediation

Upgrade Ubuntu:24.04 curl to version 8.5.0-2ubuntu10.7 or higher.

References

low severity

CVE-2025-15079

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6
  • Fixed in: 8.5.0-2ubuntu10.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.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:24.04 curl to version 8.5.0-2ubuntu10.7 or higher.

References

low severity

CVE-2025-15224

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6
  • Fixed in: 8.5.0-2ubuntu10.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.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:24.04 curl to version 8.5.0-2ubuntu10.7 or higher.

References

low severity

Open Redirect

  • Vulnerable module: curl
  • Introduced through: curl@8.5.0-2ubuntu10.6 and curl/libcurl4t64@8.5.0-2ubuntu10.6
  • Fixed in: 8.5.0-2ubuntu10.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 curl@8.5.0-2ubuntu10.6
  • Introduced through: tomcat@10-jdk17 curl/libcurl4t64@8.5.0-2ubuntu10.6

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:24.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

Upgrade Ubuntu:24.04 curl to version 8.5.0-2ubuntu10.7 or higher.

References

low severity

Covert Timing Channel

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.10.3-2build1

Detailed paths

  • Introduced through: tomcat@10-jdk17 libgcrypt20@1.10.3-2build1

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:24.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:24.04 libgcrypt20.

References

low severity
new

CVE-2026-0965

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.10.6-2ubuntu0.2
  • Fixed in: 0.10.6-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@10-jdk17 libssh/libssh-4@0.10.6-2ubuntu0.2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Ubuntu:24.04 libssh to version 0.10.6-2ubuntu0.3 or higher.

References

low severity
new

CVE-2026-0966

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.10.6-2ubuntu0.2
  • Fixed in: 0.10.6-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@10-jdk17 libssh/libssh-4@0.10.6-2ubuntu0.2

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Ubuntu:24.04 libssh to version 0.10.6-2ubuntu0.3 or higher.

References

low severity

CVE-2024-41996

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.13-0ubuntu3.7 and openssl/libssl3t64@3.0.13-0ubuntu3.7

Detailed paths

  • Introduced through: tomcat@10-jdk17 openssl@3.0.13-0ubuntu3.7
  • Introduced through: tomcat@10-jdk17 openssl/libssl3t64@3.0.13-0ubuntu3.7

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:24.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:24.04 openssl.

References

low severity

CVE-2024-56433

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.13+dfsg1-4ubuntu3.2 and shadow/passwd@1:4.13+dfsg1-4ubuntu3.2

Detailed paths

  • Introduced through: tomcat@10-jdk17 shadow/login@1:4.13+dfsg1-4ubuntu3.2
  • Introduced through: tomcat@10-jdk17 shadow/passwd@1:4.13+dfsg1-4ubuntu3.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:24.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:24.04 shadow.

References