Vulnerabilities

74 via 157 paths

Dependencies

164

Source

Group 6 Copy Created with Sketch. Docker

Target OS

ubuntu:20.04
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 2
  • 42
  • 30
Status
  • 74
  • 0
  • 0

high severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.19-3ubuntu2.4, gnupg2/gnupg@2.2.19-3ubuntu2.4 and others
  • Fixed in: 2.2.19-3ubuntu2.5+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/dirmngr@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg-l10n@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg-utils@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-agent@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-wks-client@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-wks-server@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgconf@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgsm@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgv@2.2.19-3ubuntu2.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: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

high severity

Link Following

  • Vulnerable module: git
  • Introduced through: git@1:2.25.1-1ubuntu3.14 and git/git-man@1:2.25.1-1ubuntu3.14
  • Fixed in: 1:2.25.1-1ubuntu3.14+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal git@1:2.25.1-1ubuntu3.14
  • Introduced through: maven@3-eclipse-temurin-11-focal git/git-man@1:2.25.1-1ubuntu3.14

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

medium severity

CVE-2025-6965

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.6
  • Fixed in: 3.31.1-4ubuntu0.7+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal sqlite3/libsqlite3-0@3.31.1-4ubuntu0.6

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

medium severity

Improper Encoding or Escaping of Output

  • Vulnerable module: git
  • Introduced through: git@1:2.25.1-1ubuntu3.14 and git/git-man@1:2.25.1-1ubuntu3.14

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal git@1:2.25.1-1ubuntu3.14
  • Introduced through: maven@3-eclipse-temurin-11-focal git/git-man@1:2.25.1-1ubuntu3.14

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

Double Free

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.12
  • Fixed in: 3.6.13-2ubuntu1.12+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gnutls28/libgnutls30@3.6.13-2ubuntu1.12

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

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.12
  • Fixed in: 3.6.13-2ubuntu1.12+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gnutls28/libgnutls30@3.6.13-2ubuntu1.12

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

medium severity
new

Heap-based Buffer Overflow

  • 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-eclipse-temurin-11-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

Out-of-bounds Read

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

medium severity
new

Out-of-bounds Read

  • 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-eclipse-temurin-11-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

Directory Traversal

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.3.1-5ubuntu4.7, pam/libpam-modules-bin@1.3.1-5ubuntu4.7 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal pam/libpam-modules@1.3.1-5ubuntu4.7
  • Introduced through: maven@3-eclipse-temurin-11-focal pam/libpam-modules-bin@1.3.1-5ubuntu4.7
  • Introduced through: maven@3-eclipse-temurin-11-focal pam/libpam-runtime@1.3.1-5ubuntu4.7
  • Introduced through: maven@3-eclipse-temurin-11-focal pam/libpam0g@1.3.1-5ubuntu4.7

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

medium severity

Uncontrolled Recursion

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.9-1ubuntu0.8

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal expat/libexpat1@2.2.9-1ubuntu0.8

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

medium severity
new

Out-of-bounds Read

  • 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-eclipse-temurin-11-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

medium severity

NULL Pointer Dereference

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.6.13-2ubuntu1.12
  • Fixed in: 3.6.13-2ubuntu1.12+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gnutls28/libgnutls30@3.6.13-2ubuntu1.12

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

medium severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.20.3-1ubuntu2.1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal wget@1.20.3-1ubuntu2.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: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

Reversible One-Way Hash

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.17-6ubuntu4.9, krb5/libk5crypto3@1.17-6ubuntu4.9 and others
  • Fixed in: 1.17-6ubuntu4.11

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal krb5/libgssapi-krb5-2@1.17-6ubuntu4.9
  • Introduced through: maven@3-eclipse-temurin-11-focal krb5/libk5crypto3@1.17-6ubuntu4.9
  • Introduced through: maven@3-eclipse-temurin-11-focal krb5/libkrb5-3@1.17-6ubuntu4.9
  • Introduced through: maven@3-eclipse-temurin-11-focal krb5/libkrb5support0@1.17-6ubuntu4.9

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

medium severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.9-1ubuntu0.8

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal expat/libexpat1@2.2.9-1ubuntu0.8

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

Integer Overflow or Wraparound

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.6
  • Fixed in: 3.31.1-4ubuntu0.7

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal sqlite3/libsqlite3-0@3.31.1-4ubuntu0.6

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

medium severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.19-3ubuntu2.4, gnupg2/gnupg@2.2.19-3ubuntu2.4 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/dirmngr@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg-l10n@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg-utils@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-agent@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-wks-client@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-wks-server@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgconf@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgsm@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgv@2.2.19-3ubuntu2.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: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

Race Condition

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@245.4-4ubuntu3.24 and systemd/libudev1@245.4-4ubuntu3.24
  • Fixed in: 245.4-4ubuntu3.24+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal systemd/libsystemd0@245.4-4ubuntu3.24
  • Introduced through: maven@3-eclipse-temurin-11-focal systemd/libudev1@245.4-4ubuntu3.24

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

medium severity

Out-of-bounds Write

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

medium severity

Use After Free

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

medium severity
new

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.9-1ubuntu0.8
  • Fixed in: 2.2.9-1ubuntu0.8+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal expat/libexpat1@2.2.9-1ubuntu0.8

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
new

CVE-2025-14017

  • Vulnerable module: curl
  • Introduced through: curl@7.68.0-1ubuntu2.25, curl/libcurl3-gnutls@7.68.0-1ubuntu2.25 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal curl@7.68.0-1ubuntu2.25
  • Introduced through: maven@3-eclipse-temurin-11-focal curl/libcurl3-gnutls@7.68.0-1ubuntu2.25
  • Introduced through: maven@3-eclipse-temurin-11-focal curl/libcurl4@7.68.0-1ubuntu2.25

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

There is no fixed version for Ubuntu:20.04 curl.

References

medium severity
new

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.2.9-1ubuntu0.8
  • Fixed in: 2.2.9-1ubuntu0.8+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal expat/libexpat1@2.2.9-1ubuntu0.8

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

Arbitrary Argument Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.25.1-1ubuntu3.14 and git/git-man@1:2.25.1-1ubuntu3.14
  • Fixed in: 1:2.25.1-1ubuntu3.14+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal git@1:2.25.1-1ubuntu3.14
  • Introduced through: maven@3-eclipse-temurin-11-focal git/git-man@1:2.25.1-1ubuntu3.14

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

medium severity

Buffer Overflow

  • Vulnerable module: git
  • Introduced through: git@1:2.25.1-1ubuntu3.14 and git/git-man@1:2.25.1-1ubuntu3.14
  • Fixed in: 1:2.25.1-1ubuntu3.14+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal git@1:2.25.1-1ubuntu3.14
  • Introduced through: maven@3-eclipse-temurin-11-focal git/git-man@1:2.25.1-1ubuntu3.14

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

OS Command Injection

  • Vulnerable module: git
  • Introduced through: git@1:2.25.1-1ubuntu3.14 and git/git-man@1:2.25.1-1ubuntu3.14
  • Fixed in: 1:2.25.1-1ubuntu3.14+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal git@1:2.25.1-1ubuntu3.14
  • Introduced through: maven@3-eclipse-temurin-11-focal git/git-man@1:2.25.1-1ubuntu3.14

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

medium severity
new

CVE-2025-15281

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-0ubuntu9.17, glibc/libc6@2.31-0ubuntu9.17 and others
  • Fixed in: 2.31-0ubuntu9.18+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc-bin@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc6@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/locales@2.31-0ubuntu9.17

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

CVE-2025-4802

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-0ubuntu9.17, glibc/libc6@2.31-0ubuntu9.17 and others
  • Fixed in: 2.31-0ubuntu9.18

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc-bin@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc6@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/locales@2.31-0ubuntu9.17

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

medium severity

CVE-2025-8058

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-0ubuntu9.17, glibc/libc6@2.31-0ubuntu9.17 and others
  • Fixed in: 2.31-0ubuntu9.18+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc-bin@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc6@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/locales@2.31-0ubuntu9.17

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

CVE-2026-0861

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-0ubuntu9.17, glibc/libc6@2.31-0ubuntu9.17 and others
  • Fixed in: 2.31-0ubuntu9.18+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc-bin@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc6@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/locales@2.31-0ubuntu9.17

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
new

CVE-2026-0915

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-0ubuntu9.17, glibc/libc6@2.31-0ubuntu9.17 and others
  • Fixed in: 2.31-0ubuntu9.18+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc-bin@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc6@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/locales@2.31-0ubuntu9.17

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
new

CVE-2025-66293

  • 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-eclipse-temurin-11-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

medium severity

Heap-based Buffer Overflow

  • 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-eclipse-temurin-11-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

medium severity

Out-of-bounds Read

  • 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-eclipse-temurin-11-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

Out-of-bounds Read

  • 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-eclipse-temurin-11-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

Out-of-bounds Read

  • 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-eclipse-temurin-11-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

medium severity
new

CVE-2026-0964

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

CVE-2026-0967

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

CVE-2026-0968

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

Out-of-bounds Write

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.16.0-2ubuntu0.1
  • Fixed in: 4.16.0-2ubuntu0.1+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libtasn1-6@4.16.0-2ubuntu0.1

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

CVE-2025-9230

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

medium severity

CVE-2025-52099

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.31.1-4ubuntu0.6
  • Fixed in: 3.31.1-4ubuntu0.7

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal sqlite3/libsqlite3-0@3.31.1-4ubuntu0.6

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

Directory Traversal

  • Vulnerable module: tar
  • Introduced through: tar@1.30+dfsg-7ubuntu0.20.04.4

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal tar@1.30+dfsg-7ubuntu0.20.04.4

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

low severity

Use After Free

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.31-0ubuntu9.17, glibc/libc6@2.31-0ubuntu9.17 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc-bin@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/libc6@2.31-0ubuntu9.17
  • Introduced through: maven@3-eclipse-temurin-11-focal glibc/locales@2.31-0ubuntu9.17

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

low severity
new

Off-by-one Error

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.16.0-2ubuntu0.1
  • Fixed in: 4.16.0-2ubuntu0.1+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libtasn1-6@4.16.0-2ubuntu0.1

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

low severity

CVE-2023-26604

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@245.4-4ubuntu3.24 and systemd/libudev1@245.4-4ubuntu3.24

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal systemd/libsystemd0@245.4-4ubuntu3.24
  • Introduced through: maven@3-eclipse-temurin-11-focal systemd/libudev1@245.4-4ubuntu3.24

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

low severity

CVE-2025-69421

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.34-7ubuntu0.1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-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

Uncontrolled Recursion

  • Vulnerable module: pcre3/libpcre3
  • Introduced through: pcre3/libpcre3@2:8.39-12ubuntu0.1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-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

low severity

Improper Input Validation

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.30-3ubuntu2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-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

low severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncurses6
  • Introduced through: ncurses/libncurses6@6.2-0ubuntu2.1, ncurses/libncursesw6@6.2-0ubuntu2.1 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/libncurses6@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/libncursesw6@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/libtinfo6@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/ncurses-base@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/ncurses-bin@6.2-0ubuntu2.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: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

low severity

CVE-2023-7008

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@245.4-4ubuntu3.24 and systemd/libudev1@245.4-4ubuntu3.24

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal systemd/libsystemd0@245.4-4ubuntu3.24
  • Introduced through: maven@3-eclipse-temurin-11-focal systemd/libudev1@245.4-4ubuntu3.24

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

low severity

CVE-2023-4039

  • Vulnerable module: gcc-10/gcc-10-base
  • Introduced through: gcc-10/gcc-10-base@10.5.0-1ubuntu1~20.04, gcc-10/libgcc-s1@10.5.0-1ubuntu1~20.04 and others
  • Fixed in: 10.5.0-1ubuntu1~20.04.1+esm1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gcc-10/gcc-10-base@10.5.0-1ubuntu1~20.04
  • Introduced through: maven@3-eclipse-temurin-11-focal gcc-10/libgcc-s1@10.5.0-1ubuntu1~20.04
  • Introduced through: maven@3-eclipse-temurin-11-focal gcc-10/libstdc++6@10.5.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

NULL Pointer Dereference

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.5 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.5

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal shadow/login@1:4.8.1-1ubuntu5.20.04.5
  • Introduced through: maven@3-eclipse-temurin-11-focal shadow/passwd@1:4.8.1-1ubuntu5.20.04.5

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

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.2.19-3ubuntu2.4, gnupg2/gnupg@2.2.19-3ubuntu2.4 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/dirmngr@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg-l10n@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gnupg-utils@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-agent@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-wks-client@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpg-wks-server@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgconf@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgsm@2.2.19-3ubuntu2.4
  • Introduced through: maven@3-eclipse-temurin-11-focal gnupg2/gpgv@2.2.19-3ubuntu2.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: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

low severity

Arbitrary Code Injection

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.5 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.5

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal shadow/login@1:4.8.1-1ubuntu5.20.04.5
  • Introduced through: maven@3-eclipse-temurin-11-focal shadow/passwd@1:4.8.1-1ubuntu5.20.04.5

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

low severity
new

Memory Leak

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

CVE-2025-15079

  • Vulnerable module: curl
  • Introduced through: curl@7.68.0-1ubuntu2.25, curl/libcurl3-gnutls@7.68.0-1ubuntu2.25 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal curl@7.68.0-1ubuntu2.25
  • Introduced through: maven@3-eclipse-temurin-11-focal curl/libcurl3-gnutls@7.68.0-1ubuntu2.25
  • Introduced through: maven@3-eclipse-temurin-11-focal curl/libcurl4@7.68.0-1ubuntu2.25

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

There is no fixed version for Ubuntu:20.04 curl.

References

low severity

CVE-2025-15224

  • Vulnerable module: curl
  • Introduced through: curl@7.68.0-1ubuntu2.25, curl/libcurl3-gnutls@7.68.0-1ubuntu2.25 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal curl@7.68.0-1ubuntu2.25
  • Introduced through: maven@3-eclipse-temurin-11-focal curl/libcurl3-gnutls@7.68.0-1ubuntu2.25
  • Introduced through: maven@3-eclipse-temurin-11-focal curl/libcurl4@7.68.0-1ubuntu2.25

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

There is no fixed version for Ubuntu:20.04 curl.

References

low severity

Covert Timing Channel

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.8.5-5ubuntu1.1

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-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

low severity
new

CVE-2026-0965

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

CVE-2026-0966

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.3-2ubuntu2.5
  • Fixed in: 0.9.3-2ubuntu2.5+esm3

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal libssh/libssh-4@0.9.3-2ubuntu2.5

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

CVE-2023-45918

  • Vulnerable module: ncurses/libncurses6
  • Introduced through: ncurses/libncurses6@6.2-0ubuntu2.1, ncurses/libncursesw6@6.2-0ubuntu2.1 and others

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/libncurses6@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/libncursesw6@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/libtinfo6@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/ncurses-base@6.2-0ubuntu2.1
  • Introduced through: maven@3-eclipse-temurin-11-focal ncurses/ncurses-bin@6.2-0ubuntu2.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: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
new

Failure to Sanitize Special Element

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.13

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssh/openssh-client@1:8.2p1-4ubuntu0.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: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

There is no fixed version for Ubuntu:20.04 openssh.

References

low severity
new

Improper Neutralization of Null Byte or NUL Character

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:8.2p1-4ubuntu0.13

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssh/openssh-client@1:8.2p1-4ubuntu0.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: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

There is no fixed version for Ubuntu:20.04 openssh.

References

low severity

CVE-2025-68160

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

CVE-2025-69418

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

CVE-2025-69419

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

CVE-2025-69420

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

CVE-2026-22795

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

CVE-2026-22796

  • Vulnerable module: openssl
  • Introduced through: openssl@1.1.1f-1ubuntu2.24 and openssl/libssl1.1@1.1.1f-1ubuntu2.24
  • Fixed in: 1.1.1f-1ubuntu2.24+esm2

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal openssl@1.1.1f-1ubuntu2.24
  • Introduced through: maven@3-eclipse-temurin-11-focal openssl/libssl1.1@1.1.1f-1ubuntu2.24

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

low severity

CVE-2024-56433

  • Vulnerable module: shadow/login
  • Introduced through: shadow/login@1:4.8.1-1ubuntu5.20.04.5 and shadow/passwd@1:4.8.1-1ubuntu5.20.04.5

Detailed paths

  • Introduced through: maven@3-eclipse-temurin-11-focal shadow/login@1:4.8.1-1ubuntu5.20.04.5
  • Introduced through: maven@3-eclipse-temurin-11-focal shadow/passwd@1:4.8.1-1ubuntu5.20.04.5

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.

References