Vulnerabilities

112 via 191 paths

Dependencies

144

Source

Group 6 Copy Created with Sketch. Docker

Target OS

ubuntu:22.04
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 1
  • 83
  • 28
Status
  • 112
  • 0
  • 0

high severity
new

CVE-2026-84782

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.30

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.

Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.

CWE: CWE-125: Out-of-bounds Read

Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.

The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.

Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.

The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.

FIPS impact: no The affected code is outside the FIPS module boundary.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.30 or higher.

References

medium severity

CVE-2026-13221

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.34.0-3ubuntu1.7
  • Fixed in: 5.34.0-3ubuntu1.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › perl/perl-base@5.34.0-3ubuntu1.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.10 produce silently incorrect regular expression matches when an alternation of more than 65535 fixed string branches is compiled into a trie in Perl_study_chunk.

When such branches are combined into a trie, the delta between the first branch and the shared tail is stored in a 16-bit field. A branch count above 65535 overflows the field, and the trie's match decision table is truncated with no warning or error.

A pattern of this shape produces false positive matches (matching strings it should not) and false negative matches (failing to match strings it should). When such a pattern gates an access or filtering decision, the result is wrong.

Remediation

Upgrade Ubuntu:22.04 perl to version 5.34.0-3ubuntu1.8 or higher.

References

medium severity

CVE-2026-57432

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.34.0-3ubuntu1.7
  • Fixed in: 5.34.0-3ubuntu1.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › perl/perl-base@5.34.0-3ubuntu1.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack.

S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds.

A template derived from untrusted input can read heap memory past the buffer and return it to the caller.

Remediation

Upgrade Ubuntu:22.04 perl to version 5.34.0-3ubuntu1.8 or higher.

References

medium severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity
new

Free of Memory not on the Heap

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context. An incorrect free operation can occur.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity
new

Heap-based Buffer Overflow

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.27+dfsg2-3ubuntu1.2 and cyrus-sasl2/libsasl2-modules-db@2.1.27+dfsg2-3ubuntu1.2

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › cyrus-sasl2/libsasl2-2@2.1.27+dfsg2-3ubuntu1.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › cyrus-sasl2/libsasl2-modules-db@2.1.27+dfsg2-3ubuntu1.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream cyrus-sasl2 package and not the cyrus-sasl2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A heap-based buffer overflow flaw was found in Cyrus SASL. The add_to_challenge() function in the DIGEST-MD5 plugin computes the size of the buffer needed for a challenge/response field before DIGEST-MD5 quoting is applied, but does not recompute that size when quoting (escaping special characters) makes the value longer. The under-sized buffer is then passed to strcat(), causing a heap-based out-of-bounds write whose size depends on attacker-controlled input. A malicious or on-path DIGEST-MD5 (or HTTP Digest) server can trigger this flaw in a connecting client by supplying a crafted challenge field, such as realm or nonce, most likely resulting in a crash of the client application.

Remediation

There is no fixed version for Ubuntu:22.04 cyrus-sasl2.

References

medium severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.

Remediation

There is no fixed version for Ubuntu:22.04 expat.

References

medium severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Expat through 2.8.3 contains an out-of-bounds read vulnerability that allows attackers to trigger memory corruption by processing XML with external entity parsers created via XML_ExternalEntityParserCreate. A struct size mismatch between ELEMENT_TYPE members causes storeAtts to read the attIndex member past allocated memory boundaries, resulting in failure to normalize whitespace in non-CDATA attributes or a wild pointer dereference causing a segfault. This vulnerability was introduced by the fix for CVE-2026-66046.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Incorrect Check of Function Return Value

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.6-2ubuntu0.22.04.7
  • Fixed in: 0.9.6-2ubuntu0.22.04.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libssh/libssh-4@0.9.6-2ubuntu0.22.04.7

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

A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.

Remediation

Upgrade Ubuntu:22.04 libssh to version 0.9.6-2ubuntu0.22.04.8 or higher.

References

medium severity

Use After Free

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.6-2ubuntu0.22.04.7
  • Fixed in: 0.9.6-2ubuntu0.22.04.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libssh/libssh-4@0.9.6-2ubuntu0.22.04.7

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

A flaw was found in libssh. If data packets are processed after a channel is closed, channel data callbacks can be invoked after the associated data has already been freed, leading to crashes or possible use-after-free conditions.

Remediation

Upgrade Ubuntu:22.04 libssh to version 0.9.6-2ubuntu0.22.04.8 or higher.

References

medium severity
new

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.2.11.dfsg-2ubuntu9.2

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › zlib/zlib1g@1:1.2.11.dfsg-2ubuntu9.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

zlib versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vulnerability in the gz_vacate() function when processing non-blocking gzwrite() operations with stale external buffer pointers. Attackers can trigger the overflow by calling gzprintf() or gzvprintf() after a write stall, causing an unchecked memmove() to write beyond the internal input buffer boundary.

Remediation

There is no fixed version for Ubuntu:22.04 zlib.

References

medium severity

Link Following

  • Vulnerable module: attr/libattr1
  • Introduced through: attr/libattr1@1:2.5.1-1build1
  • Fixed in: 1:2.5.1-1ubuntu0.1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › attr/libattr1@1:2.5.1-1build1

NVD Description

Note: Versions mentioned in the description apply only to the upstream attr package and not the attr package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can redirect getfattr and setfattr operations to arbitrary files by substituting a symlink, leading to local privilege escalation when getfattr or setfattr is invoked by a privileged process over an attacker-controlled path.

Remediation

Upgrade Ubuntu:22.04 attr to version 1:2.5.1-1ubuntu0.1 or higher.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.6-2ubuntu0.22.04.7
  • Fixed in: 0.9.6-2ubuntu0.22.04.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libssh/libssh-4@0.9.6-2ubuntu0.22.04.7

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

A flaw was found in libssh. A remote authenticated peer can advertise a zero maximum packet size in SSH_MSG_CHANNEL_OPEN, causing later channel writes to loop indefinitely and consume CPU, leading to denial of service.

Remediation

Upgrade Ubuntu:22.04 libssh to version 0.9.6-2ubuntu0.22.04.8 or higher.

References

medium severity
new

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity
new

Out-of-bounds Read

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity

Heap-based Buffer Overflow

  • Vulnerable module: p11-kit
  • Introduced through: p11-kit@0.24.0-6build1, p11-kit/libp11-kit0@0.24.0-6build1 and others
  • Fixed in: 0.24.0-6ubuntu0.1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › p11-kit@0.24.0-6build1
  • Introduced through: tomcat@9-jre8-temurin-jammy › p11-kit/libp11-kit0@0.24.0-6build1
  • Introduced through: tomcat@9-jre8-temurin-jammy › p11-kit/p11-kit-modules@0.24.0-6build1

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in p11-kit. A local attacker, or one with equivalent access to a reachable RPC channel, could exploit an integer overflow vulnerability. By sending specially crafted messages, the attacker can cause the system to miscalculate memory allocation for nested attributes. This leads to a memory corruption issue, specifically a heap out-of-bounds write, which can crash the p11-kit RPC parsing process, resulting in a Denial of Service (DoS). This vulnerability is only exploitable on 32 bit systems.

Remediation

Upgrade Ubuntu:22.04 p11-kit to version 0.24.0-6ubuntu0.1 or higher.

References

medium severity

Uncontrolled Recursion

  • Vulnerable module: p11-kit
  • Introduced through: p11-kit@0.24.0-6build1, p11-kit/libp11-kit0@0.24.0-6build1 and others
  • Fixed in: 0.24.0-6ubuntu0.1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › p11-kit@0.24.0-6build1
  • Introduced through: tomcat@9-jre8-temurin-jammy › p11-kit/libp11-kit0@0.24.0-6build1
  • Introduced through: tomcat@9-jre8-temurin-jammy › p11-kit/p11-kit-modules@0.24.0-6build1

NVD Description

Note: Versions mentioned in the description apply only to the upstream p11-kit package and not the p11-kit package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.

Remediation

Upgrade Ubuntu:22.04 p11-kit to version 0.24.0-6ubuntu0.1 or higher.

References

medium severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.21.2-2ubuntu1.4

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › wget@1.21.2-2ubuntu1.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream wget package and not the wget package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

Remediation

There is no fixed version for Ubuntu:22.04 wget.

References

medium severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

Detection of Error Condition Without Action

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.6-2ubuntu0.22.04.7
  • Fixed in: 0.9.6-2ubuntu0.22.04.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libssh/libssh-4@0.9.6-2ubuntu0.22.04.7

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

A flaw was found in libssh. When ProxyCommand is used, an unchecked fork() failure can be stored as process ID -1; during cleanup, signals may then be sent across the caller's accessible process tree, leading to local denial of service.

Remediation

Upgrade Ubuntu:22.04 libssh to version 0.9.6-2ubuntu0.22.04.8 or higher.

References

medium severity
new

Out-of-bounds Read

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity
new

Inefficient Regular Expression Complexity

  • Vulnerable module: dash
  • Introduced through: dash@0.5.11+git20210903+057cd650a4ed-3build1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › dash@0.5.11+git20210903+057cd650a4ed-3build1

NVD Description

Note: Versions mentioned in the description apply only to the upstream dash package and not the dash package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in dash. When built without libc fnmatch, the internal pmatch() matcher implements * by unbounded recursion over candidate positions. A local user who can plant filenames, or otherwise feed that matcher, can make a short multi-star pattern such as ....*.tar.gz consume excessive CPU.

Remediation

There is no fixed version for Ubuntu:22.04 dash.

References

medium severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.

Remediation

There is no fixed version for Ubuntu:22.04 expat.

References

medium severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.7.5 allows an infinite loop while parsing DTD content.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity
new

Resource Exhaustion

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.11.1+dfsg-1ubuntu0.3
  • Fixed in: 2.11.1+dfsg-1ubuntu0.4

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › freetype/libfreetype6@2.11.1+dfsg-1ubuntu0.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream freetype package and not the freetype package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in FreeType, specifically within its CID font loader. A remote attacker could exploit this vulnerability by tricking a user into opening content that embeds or references a specially crafted CID-keyed font. This crafted font can cause repeated allocations and decryptions of subroutine data across multiple font dictionaries, leading to excessive memory and CPU consumption. This can result in a denial of service (DoS) for the application or service processing the font, potentially causing it to hang or terminate.

Remediation

Upgrade Ubuntu:22.04 freetype to version 2.11.1+dfsg-1ubuntu0.4 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.6-2ubuntu0.22.04.7
  • Fixed in: 0.9.6-2ubuntu0.22.04.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libssh/libssh-4@0.9.6-2ubuntu0.22.04.7

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

A flaw was found in libssh. A malicious SFTP server can send responses for unknown request IDs that libssh clients keep queued indefinitely, causing unbounded memory growth and client-side denial of service.

Remediation

Upgrade Ubuntu:22.04 libssh to version 0.9.6-2ubuntu0.22.04.8 or higher.

References

medium severity

Use After Free

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.37.2-4ubuntu3.5, util-linux/libblkid1@2.37.2-4ubuntu3.5 and others
  • Fixed in: 2.37.2-4ubuntu3.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libblkid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libmount1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libsmartcols1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libuuid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/mount@2.37.2-4ubuntu3.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in the libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service.

Remediation

Upgrade Ubuntu:22.04 util-linux to version 2.37.2-4ubuntu3.6 or higher.

References

medium severity

Link Following

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1ubuntu0.1.22.04.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › tar@1.34+dfsg-1ubuntu0.1.22.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction.

Remediation

There is no fixed version for Ubuntu:22.04 tar.

References

medium severity

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

  • Vulnerable module: tar
  • Introduced through: tar@1.34+dfsg-1ubuntu0.1.22.04.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › tar@1.34+dfsg-1ubuntu0.1.22.04.6

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.

Remediation

There is no fixed version for Ubuntu:22.04 tar.

References

medium severity
new

Out-of-bounds Write

  • Vulnerable module: dash
  • Introduced through: dash@0.5.11+git20210903+057cd650a4ed-3build1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › dash@0.5.11+git20210903+057cd650a4ed-3build1

NVD Description

Note: Versions mentioned in the description apply only to the upstream dash package and not the dash package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in dash. The printf builtin reserves four bytes before converting a Unicode \u or \U escape, but the multi-byte token can need five or six bytes. A local user who can supply such an escape to dash printf or echo %b, including through dash -c and a positional argument, can write one or two bytes past that reservation.

Remediation

There is no fixed version for Ubuntu:22.04 dash.

References

medium severity

OS Command Injection

  • Vulnerable module: libssh/libssh-4
  • Introduced through: libssh/libssh-4@0.9.6-2ubuntu0.22.04.7
  • Fixed in: 0.9.6-2ubuntu0.22.04.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libssh/libssh-4@0.9.6-2ubuntu0.22.04.7

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

A flaw was found in libssh. A malicious username expanded through %r in ProxyCommand handling can inject shell metacharacters, exposing environment variables and causing unintended shell behavior.

Remediation

Upgrade Ubuntu:22.04 libssh to version 0.9.6-2ubuntu0.22.04.8 or higher.

References

medium severity

Authentication Bypass

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25
  • Fixed in: 7.81.0-1ubuntu1.26

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.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:22.04 relevant fixed versions and status.

Successfully using libcurl to do a transfer to a specific HTTP origin (hostA) with Digest authentication and then changing the origin to a different one (hostB) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the Authorization: header field meant for hostA, to hostB.

Remediation

Upgrade Ubuntu:22.04 curl to version 7.81.0-1ubuntu1.26 or higher.

References

medium severity

CVE-2026-18924

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25
  • Fixed in: 7.81.0-1ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.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:22.04 relevant fixed versions and status.

A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.

Remediation

Upgrade Ubuntu:22.04 curl to version 7.81.0-1ubuntu1.29 or higher.

References

medium severity

CVE-2026-19931

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.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:22.04 relevant fixed versions and status.

A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

medium severity

CVE-2026-80230

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25
  • Fixed in: 7.81.0-1ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.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:22.04 relevant fixed versions and status.

When CURLOPT_PINNEDPUBLICKEY is configured alongside options that disable standard peer verification (CURLOPT_SSL_VERIFYPEER = 0 and CURLOPT_SSL_VERIFYHOST = 0), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.

Remediation

Upgrade Ubuntu:22.04 curl to version 7.81.0-1ubuntu1.29 or higher.

References

medium severity

CVE-2026-82209

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25
  • Fixed in: 7.81.0-1ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.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:22.04 relevant fixed versions and status.

When libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a Set-Cookie header where the Domain attribute explicitly matches an origin host that is itself a public suffix (e.g., Domain=co.uk set by co.uk).

Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (.co.uk). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., attacker.co.uk).

Remediation

Upgrade Ubuntu:22.04 curl to version 7.81.0-1ubuntu1.29 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: diffutils
  • Introduced through: diffutils@1:3.8-0ubuntu2
  • Fixed in: 1:3.8-0ubuntu2.1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › diffutils@1:3.8-0ubuntu2

NVD Description

Note: Versions mentioned in the description apply only to the upstream diffutils package and not the diffutils package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

diff3 tool from GNU diffutils is vulnerable to a heap‑based buffer overflow due to multiple signed integer overflows in line‑mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds. When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out‑of‑bounds writes during internal processing.  An attacker who can control the output of the diff program used by diff3 (e.g. via --diff-program pointing to a malicious script) can trigger out-of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment.

This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815 

NOTE: The project maintainers claim that this is not a security issue. They state that the worst outcome this issue can cause is a crash of diff and that it cannot be used to escalate privileges.

Remediation

Upgrade Ubuntu:22.04 diffutils to version 1:3.8-0ubuntu2.1 or higher.

References

medium severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.

Remediation

There is no fixed version for Ubuntu:22.04 expat.

References

medium severity

Incorrect Synchronization

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Insufficient Entropy

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.

Remediation

There is no fixed version for Ubuntu:22.04 expat.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 has an integer overflow in addBinding.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 has an integer overflow in copyString.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 has an integer overflow in getAttributeId.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 has an integer overflow in storeAtts.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur (similar to the CVE-2026-50219 situation).

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.9 or higher.

References

medium severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.4.7-1ubuntu0.7
  • Fixed in: 2.4.7-1ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › expat/libexpat1@2.4.7-1ubuntu0.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream expat package and not the expat package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.

Remediation

Upgrade Ubuntu:22.04 expat to version 2.4.7-1ubuntu0.8 or higher.

References

medium severity

CVE-2026-18374

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Passing an effectively empty string to the ,ccs= syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled.

This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for ccs should not pass them through without validation.

Remediation

There is no fixed version for Ubuntu:22.04 glibc.

References

medium severity

CVE-2026-19542

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others
  • Fixed in: 2.35-0ubuntu3.15

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Calling tdelete on a sufficiently deep tree in the GNU C Library version 2.1 to 2.44 may write one pointer past the end of an alloca-allocated array on the stack, which may crash the application.

The tdelete implementation keeps an explicit stack of parent nodes for rebalancing, which is grown as needed while descending the tree. Two rebalancing branches push an additional entry without checking the capacity, and write past the array when the stack is exactly full. Triggering this requires a node at a depth of exactly 40 (or 40 plus a multiple of 20), which implies a tree with at least a million nodes, so an attacker must drive a large number of insertions and deletions through an application that uses tsearch and tdelete. The written value is a pointer into a tree node and is not directly attacker controlled. No affected application in common distributions has been identified.

Remediation

Upgrade Ubuntu:22.04 glibc to version 2.35-0ubuntu3.15 or higher.

References

medium severity

CVE-2026-6368

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others
  • Fixed in: 2.35-0ubuntu3.15

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

Remediation

Upgrade Ubuntu:22.04 glibc to version 2.35-0ubuntu3.15 or higher.

References

medium severity

CVE-2026-6791

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others
  • Fixed in: 2.35-0ubuntu3.15

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.

Remediation

Upgrade Ubuntu:22.04 glibc to version 2.35-0ubuntu3.15 or higher.

References

medium severity

CVE-2026-77117

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others
  • Fixed in: 2.35-0ubuntu3.15

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.

Some SHIFT_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used. The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.

Remediation

Upgrade Ubuntu:22.04 glibc to version 2.35-0ubuntu3.15 or higher.

References

medium severity

CVE-2026-80489

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others
  • Fixed in: 2.35-0ubuntu3.15

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.

Some EUC_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the EUC_JISX0213 character set is affected, which is not commonly used. The related defect in SHIFT_JISX0213 converter is tracked separately as CVE-2026-77117.

Remediation

Upgrade Ubuntu:22.04 glibc to version 2.35-0ubuntu3.15 or higher.

References

medium severity
new

CVE-2026-89092

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.35-0ubuntu3.14, glibc/libc6@2.35-0ubuntu3.14 and others

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc-bin@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/libc6@2.35-0ubuntu3.14
  • Introduced through: tomcat@9-jre8-temurin-jammy › glibc/locales@2.35-0ubuntu3.14

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system.

Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack.  During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server.  In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated.

There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash.

Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.

Remediation

There is no fixed version for Ubuntu:22.04 glibc.

References

medium severity
new

CVE-2026-67693

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.3-4ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › gnutls28/libgnutls30@3.7.3-4ubuntu1.9

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

An issue in gnutls v.3.8.13 allows an attacker to obtain sensitive information via failing to reject end-entity X.509 certificates that contain a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU)

Remediation

There is no fixed version for Ubuntu:22.04 gnutls28.

References

medium severity
new

CVE-2026-88647

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.3-4ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › gnutls28/libgnutls30@3.7.3-4ubuntu1.9

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

A hostname verification bypass in GnuTLS v3.8.13 allows attackers to circumvent the Common Name fallback mechanism and eavesdrop on communications via a crafted certificate.

Remediation

There is no fixed version for Ubuntu:22.04 gnutls28.

References

medium severity
new

CVE-2026-95184

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.3-4ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › gnutls28/libgnutls30@3.7.3-4ubuntu1.9

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

Improper certificate validation in gnutls v3.8.13 causes the application to reject legitimate certificates for valid users, leading to a Denial of Service (DoS).

Remediation

There is no fixed version for Ubuntu:22.04 gnutls28.

References

medium severity
new

CVE-2026-95209

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.3-4ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › gnutls28/libgnutls30@3.7.3-4ubuntu1.9

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

An issue in gnutls v3.8.13 causes legitimate CA certificates to be rejected, leading to a Denial of Service (DoS).

Remediation

There is no fixed version for Ubuntu:22.04 gnutls28.

References

medium severity
new

CVE-2026-95210

  • Vulnerable module: gnutls28/libgnutls30
  • Introduced through: gnutls28/libgnutls30@3.7.3-4ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › gnutls28/libgnutls30@3.7.3-4ubuntu1.9

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

Improper certificate validation in gnutls v3.8.13 causes the application to accept certificates containing invalid extensions.

Remediation

There is no fixed version for Ubuntu:22.04 gnutls28.

References

medium severity
new

CVE-2026-46675

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.37-3ubuntu0.5
  • Fixed in: 1.6.37-3ubuntu0.7

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libpng1.6/libpng16-16@1.6.37-3ubuntu0.5

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Ubuntu:22.04 libpng1.6 to version 1.6.37-3ubuntu0.7 or higher.

References

medium severity

Interpretation Conflict

  • Vulnerable module: libpng1.6/libpng16-16
  • Introduced through: libpng1.6/libpng16-16@1.6.37-3ubuntu0.5
  • Fixed in: 1.6.37-3ubuntu0.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libpng1.6/libpng16-16@1.6.37-3ubuntu0.5

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

LIBPNG is a reference library for use in applications that process PNG (Portable Network Graphics) raster image files. In version 1.8.0, three inter-frame chunk discard paths in the push-mode APNG parser clear the chunk-header flag without consuming the chunk body and CRC, allowing attacker-controlled bytes inside an ignored ancillary chunk to be reinterpreted as a fresh chunk header on the next call to png_process_data. Commit faf06924688b62d7c1654b5ceddedbde66ffadb4 fixes the issue.

Remediation

Upgrade Ubuntu:22.04 libpng1.6 to version 1.6.37-3ubuntu0.6 or higher.

References

medium severity

CVE-2026-63072

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write.

Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service.

CWE: CWE-787: Out-of-bounds Write

Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure.

The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation.

FIPS impact: no

As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.29 or higher.

References

medium severity

CVE-2026-63076

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer.

Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service.

CWE: CWE-476: NULL Pointer Dereference

Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted.

This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable.

FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.29 or higher.

References

medium severity
new

Improper Protection of Alternate Path

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity
new

Out-of-bounds Write

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with arbitrary data.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

medium severity

CVE-2026-12087

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.34.0-3ubuntu1.7
  • Fixed in: 5.34.0-3ubuntu1.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › perl/perl-base@5.34.0-3ubuntu1.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Socket versions before 2.041 for Perl have an out-of-bounds heap read.

In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer.

Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.

Remediation

Upgrade Ubuntu:22.04 perl to version 5.34.0-3ubuntu1.8 or higher.

References

medium severity

CVE-2026-15534

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.34.0-3ubuntu1.7
  • Fixed in: 5.34.0-3ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › perl/perl-base@5.34.0-3ubuntu1.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Perl versions through 5.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch.

The regex engine's superlinear cache holds one bit per subject position for each participating WHILEM node, so the bit count is the subject length plus one times the number of nodes. Nothing checks that product for positive overflow of the signed 32-bit count: a 286331153 byte subject matched against a pattern with 15 participating nodes stores the count as 14, leaving a two byte cache. The cache is then indexed from the real match position and node number, so reads go past the end of the allocation, and on failure CACHEsayNO sets a bit past it.

A caller that matches an attacker controlled subject of this size against a pattern of this shape can crash the process or corrupt heap memory.

Remediation

Upgrade Ubuntu:22.04 perl to version 5.34.0-3ubuntu1.9 or higher.

References

medium severity

CVE-2026-19487

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.34.0-3ubuntu1.7
  • Fixed in: 5.34.0-3ubuntu1.9

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › perl/perl-base@5.34.0-3ubuntu1.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Perl versions from 5.9.4 before 5.41.9 produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass.

The prescan walks the subject for positions where the full pattern could match, and the engine tries it from the leftmost one recorded. A failing transition sets the failed flag, and a later successful transition does not clear it, so the prescan reads the stale flag as a failure and stops before it can record a candidate that starts earlier. It takes a subject where one candidate is recorded and a later character then forces a fallback through a fail link that succeeds.

Example:

"ABCDE" =~ m/ABCF|BCDE|C/; # matches C at offset 2, not BCDE "ABCDE" =~ m/ABCF|BCDE|C(G)/; # no match, BCDE missed

An alternation like this can miss input it should match, or match it on the wrong branch, so an access or filtering decision made from the result can be wrong.

Remediation

Upgrade Ubuntu:22.04 perl to version 5.34.0-3ubuntu1.9 or higher.

References

medium severity

CVE-2026-57433

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.34.0-3ubuntu1.7
  • Fixed in: 5.34.0-3ubuntu1.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › perl/perl-base@5.34.0-3ubuntu1.7

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Storable versions before 3.41 for Perl have a signed integer overflow when deserializing a crafted SX_HOOK record.

retrieve_hook_common reads a signed 32-bit item count from an SX_HOOK record and calls av_extend with that count plus one. A count of I32_MAX wraps the addition to a negative value.

A crafted blob passed to thaw or retrieve triggers the overflow; av_extend receives the negative count and dies with a panic, terminating the deserialization.

Remediation

Upgrade Ubuntu:22.04 perl to version 5.34.0-3ubuntu1.8 or higher.

References

medium severity

CVE-2026-39113

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.37.2-2ubuntu0.7
  • Fixed in: 3.37.2-2ubuntu0.8

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › sqlite3/libsqlite3-0@3.37.2-2ubuntu0.7

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

Buffer Overflow vulnerability in SQLite affected version source snapshots/builds containing Fossil check-in 8bdc0d485e3ad0c7a1e818da66f106951d496b05cbe61d12c2c448f2f24b6d5d (Git mirror 169f68ed88b34cb68f720191c64c058f2ccec508, 2026-03-11) and later snapshots/builds allows an attacker to cause a denial of service via the ext/misc/sqlar.c, sqlarUncompressFunc(), sqlar_uncompress(), sqlite3_value_int64(), sqlite3_malloc(int), uncompress() components

Remediation

Upgrade Ubuntu:22.04 sqlite3 to version 3.37.2-2ubuntu0.8 or higher.

References

medium severity

CVE-2026-15059

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@249.11-0ubuntu3.21 and systemd/libudev1@249.11-0ubuntu3.21
  • Fixed in: 249.11-0ubuntu3.22

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › systemd/libsystemd0@249.11-0ubuntu3.21
  • Introduced through: tomcat@9-jre8-temurin-jammy › systemd/libudev1@249.11-0ubuntu3.21

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.

Remediation

Upgrade Ubuntu:22.04 systemd to version 249.11-0ubuntu3.22 or higher.

References

medium severity

CVE-2026-16742

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@249.11-0ubuntu3.21 and systemd/libudev1@249.11-0ubuntu3.21
  • Fixed in: 249.11-0ubuntu3.22

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › systemd/libsystemd0@249.11-0ubuntu3.21
  • Introduced through: tomcat@9-jre8-temurin-jammy › systemd/libudev1@249.11-0ubuntu3.21

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user

Remediation

Upgrade Ubuntu:22.04 systemd to version 249.11-0ubuntu3.22 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.37.2-4ubuntu3.5, util-linux/libblkid1@2.37.2-4ubuntu3.5 and others
  • Fixed in: 2.37.2-4ubuntu3.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libblkid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libmount1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libsmartcols1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libuuid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/mount@2.37.2-4ubuntu3.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

util-linux is a random collection of Linux utilities. Before util-linux 2.41.4, parse_dos_extended() in libblkid/src/partitions/dos.c computes an extended-partition start sector with 32-bit addition and does not apply the extended-area bounds checks to the first two EBR entries. A local attacker who causes a crafted DOS extended-partition disk image or removable medium to be probed can wrap cur_start + start to sector zero and cause libblkid to report a false partition overlapping the MBR. This directly compromises the integrity of the reported partition metadata; disk modification or availability loss requires a separate downstream consumer to act on that metadata. This issue is fixed in 2.41.4.

Remediation

Upgrade Ubuntu:22.04 util-linux to version 2.37.2-4ubuntu3.6 or higher.

References

medium severity

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

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.37.2-4ubuntu3.5, util-linux/libblkid1@2.37.2-4ubuntu3.5 and others
  • Fixed in: 2.37.2-4ubuntu3.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libblkid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libmount1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libsmartcols1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libuuid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/mount@2.37.2-4ubuntu3.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.

Remediation

Upgrade Ubuntu:22.04 util-linux to version 2.37.2-4ubuntu3.6 or higher.

References

medium severity

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

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.37.2-4ubuntu3.5, util-linux/libblkid1@2.37.2-4ubuntu3.5 and others
  • Fixed in: 2.37.2-4ubuntu3.6

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libblkid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libmount1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libsmartcols1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/libuuid1@2.37.2-4ubuntu3.5
  • Introduced through: tomcat@9-jre8-temurin-jammy › util-linux/mount@2.37.2-4ubuntu3.5

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

util-linux is a random collection of Linux utilities. In util-linux 2.17 through 2.41.6 and 2.42 through 2.42.3, and in 2.42.4 when the legacy mount(2) path is used without /proc, restricted non-root mount requests validate an /etc/fstab target before the mount operation re-resolves that pathname. A local low-privileged user authorized by an fstab user or users entry whose target has an attacker-writable ancestor can use renameat2(RENAME_EXCHANGE) to swap a path component and redirect an authorized mount to a root-owned location, such as mounting attacker-controlled content over /etc/sudoers.d, and thereby gain root privileges. Versions 2.41.5 and 2.42.2 pin targets for the new mount API, and 2.42.4 pins legacy targets through /proc/self/fd; the documented legacy fallback without /proc remains affected.

Remediation

Upgrade Ubuntu:22.04 util-linux to version 2.37.2-4ubuntu3.6 or higher.

References

low severity

Resource Exhaustion

  • Vulnerable module: libzstd/libzstd1
  • Introduced through: libzstd/libzstd1@1.4.8+dfsg-3build1

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › pcre2/libpcre2-8-0@10.39-3ubuntu0.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream pcre2 package and not the pcre2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Integer overflow vulnerability in pcre2test before 10.41 allows attackers to cause a denial of service or other unspecified impacts via negative input.

Remediation

There is no fixed version for Ubuntu:22.04 pcre2.

References

low severity

CVE-2023-50495

  • Vulnerable module: ncurses/libncurses6
  • Introduced through: ncurses/libncurses6@6.3-2ubuntu0.2, ncurses/libncursesw6@6.3-2ubuntu0.2 and others

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/libncurses6@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/libncursesw6@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/libtinfo6@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/ncurses-base@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/ncurses-bin@6.3-2ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().

Remediation

There is no fixed version for Ubuntu:22.04 ncurses.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: gcc-12/gcc-12-base
  • Introduced through: gcc-12/gcc-12-base@12.3.0-1ubuntu1~22.04.3, gcc-12/libgcc-s1@12.3.0-1ubuntu1~22.04.3 and others

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › gcc-12/gcc-12-base@12.3.0-1ubuntu1~22.04.3
  • Introduced through: tomcat@9-jre8-temurin-jammy › gcc-12/libgcc-s1@12.3.0-1ubuntu1~22.04.3
  • Introduced through: tomcat@9-jre8-temurin-jammy › gcc-12/libstdc++6@12.3.0-1ubuntu1~22.04.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.

Remediation

There is no fixed version for Ubuntu:22.04 gcc-12.

References

low severity

Stack-based Buffer Overflow

  • Vulnerable module: coreutils
  • Introduced through: coreutils@8.32-4.1ubuntu1.3
  • Fixed in: 8.32-4.1ubuntu1.4

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › coreutils@8.32-4.1ubuntu1.3

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.

Remediation

Upgrade Ubuntu:22.04 coreutils to version 8.32-4.1ubuntu1.4 or higher.

References

low severity

Out-of-Bounds

  • Vulnerable module: ncurses/libncurses6
  • Introduced through: ncurses/libncurses6@6.3-2ubuntu0.2, ncurses/libncursesw6@6.3-2ubuntu0.2 and others
  • Fixed in: 6.3-2ubuntu0.3

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/libncurses6@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/libncursesw6@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/libtinfo6@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/ncurses-base@6.3-2ubuntu0.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › ncurses/ncurses-bin@6.3-2ubuntu0.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A vulnerability has been found in GNU ncurses up to 6.5-20250322 and classified as problematic. This vulnerability affects the function postprocess_termcap of the file tinfo/parse_entry.c. The manipulation leads to stack-based buffer overflow. The attack needs to be approached locally. Upgrading to version 6.5-20250329 is able to address this issue. It is recommended to upgrade the affected component.

Remediation

Upgrade Ubuntu:22.04 ncurses to version 6.3-2ubuntu0.3 or higher.

References

low severity

Arbitrary Code Injection

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › shadow/login@1:4.8.1-2ubuntu2.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › shadow/passwd@1:4.8.1-2ubuntu2.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.

Remediation

There is no fixed version for Ubuntu:22.04 shadow.

References

low severity

Incorrect Resource Transfer Between Spheres

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@249.11-0ubuntu3.21 and systemd/libudev1@249.11-0ubuntu3.21

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › systemd/libsystemd0@249.11-0ubuntu3.21
  • Introduced through: tomcat@9-jre8-temurin-jammy › systemd/libudev1@249.11-0ubuntu3.21

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.

Remediation

There is no fixed version for Ubuntu:22.04 systemd.

References

low severity

Out-of-bounds Write

  • Vulnerable module: bzip2/libbz2-1.0
  • Introduced through: bzip2/libbz2-1.0@1.0.8-5build1
  • Fixed in: 1.0.8-5ubuntu0.1

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › bzip2/libbz2-1.0@1.0.8-5build1

NVD Description

Note: Versions mentioned in the description apply only to the upstream bzip2 package and not the bzip2 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

bzip2 contains an off‑by‑one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out‑of‑bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).

This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67

Remediation

Upgrade Ubuntu:22.04 bzip2 to version 1.0.8-5ubuntu0.1 or higher.

References

low severity
new

CVE-2026-86409

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity
new

CVE-2026-86414

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity
new

CVE-2026-87862

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity
new

CVE-2026-87864

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity

CVE-2026-8932

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25
  • Fixed in: 7.81.0-1ubuntu1.27

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.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:22.04 relevant fixed versions and status.

libcurl would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.

libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.

Remediation

Upgrade Ubuntu:22.04 curl to version 7.81.0-1ubuntu1.27 or higher.

References

low severity
new

CVE-2026-92388

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity
new

CVE-2026-92389

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity
new

CVE-2026-92391

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity
new

CVE-2026-94266

  • Vulnerable module: curl
  • Introduced through: curl@7.81.0-1ubuntu1.25 and curl/libcurl4@7.81.0-1ubuntu1.25

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › curl@7.81.0-1ubuntu1.25
  • Introduced through: tomcat@9-jre8-temurin-jammy › curl/libcurl4@7.81.0-1ubuntu1.25

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Ubuntu:22.04 curl.

References

low severity

Covert Timing Channel

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.9.4-3ubuntu3.2
  • Fixed in: 1.9.4-3ubuntu3.3

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › libgcrypt20@1.9.4-3ubuntu3.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream libgcrypt20 package and not the libgcrypt20 package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

Upgrade Ubuntu:22.04 libgcrypt20 to version 1.9.4-3ubuntu3.3 or higher.

References

low severity
new

CVE-2026-35189

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.30

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions.

Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations.

The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received.

FIPS impact: no The affected code is outside the FIPS module boundary.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.30 or higher.

References

low severity
new

CVE-2026-54872

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.30

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing.

Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.

CWE: CWE-208: Observable Timing Discrepancy

Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce.

The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1.

Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue.

The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected.

FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.30 or higher.

References

low severity

CVE-2026-54874

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires.

Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service.

CWE: CWE-405: Asymmetric Resource Consumption (Amplification)

Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up.

Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network.

An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity.

FIPS impact: no

No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.

Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr

This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell.

-- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.29 or higher.

References

low severity

CVE-2026-63074

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth.

Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely.

The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all.

FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.29 or higher.

References

low severity

CVE-2026-75803

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.29

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function.

Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages.

CWE: CWE-354 (Improper Validation of Integrity Check Value)

Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case.

FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected algorithms are not FIPS approved and thus not implemented in the FIPS module.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.29 or higher.

References

low severity
new

CVE-2026-75805

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.30

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response.

Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application.

CWE: CWE-476: NULL-pointer dereference

Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API.

A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash.

The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected.

FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.30 or higher.

References

low severity
new

CVE-2026-75806

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.30

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead.

Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact.

CWE: CWE-1284: Improper Validation of Specified Quantity in Input

Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication.

In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS.

The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record.

FIPS impact: no The affected code is outside the FIPS module boundary.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.30 or higher.

References

low severity
new

CVE-2026-77696

  • Vulnerable module: openssl
  • Introduced through: openssl@3.0.2-0ubuntu1.26 and openssl/libssl3@3.0.2-0ubuntu1.26
  • Fixed in: 3.0.2-0ubuntu1.30

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl@3.0.2-0ubuntu1.26
  • Introduced through: tomcat@9-jre8-temurin-jammy › openssl/libssl3@3.0.2-0ubuntu1.26

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

Issue summary: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel.

Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.

CWE: CWE-208: Observable Timing Discrepancy

Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel.

Applications performing SM2 signature generation are affected on all platforms.

FIPS Impact: no SM2 is not a FIPS algorithm.

Remediation

Upgrade Ubuntu:22.04 openssl to version 3.0.2-0ubuntu1.30 or higher.

References

low severity

CVE-2024-56433

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

Detailed paths

  • Introduced through: tomcat@9-jre8-temurin-jammy › shadow/login@1:4.8.1-2ubuntu2.2
  • Introduced through: tomcat@9-jre8-temurin-jammy › shadow/passwd@1:4.8.1-2ubuntu2.2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Ubuntu. See How to fix? for Ubuntu:22.04 relevant fixed versions and status.

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Remediation

There is no fixed version for Ubuntu:22.04 shadow.

References