Threats Tagged 'ubuntu-pro-18-04-lts'

This update includes the following RPMs: openssl: * openssl-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-config-fips-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-devel-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-devel-engine-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-fips-provider-upstream-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-libs-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-perl-3.5.8-0.1.hum1 (aarch64, x86_64) * openssl-3.5.8-0.1.hum1.src (src)

QUIC Server May Trigger Double Free When Processing INITIAL Packet

Excessive Memory Use Buffering DTLS Records for a Future Epoch

Heap Buffer Overflow in CMS Key Unwrapping

CMP Indefinite Cache Growth of ExtraCerts

QUIC ACK-only Packet Retention Can Cause Memory Exhaustion

Invalid Pointer Dereference in CMP Server via Crafted protectionAlg

The URLS regular expression in nltk/tokenize/casual.py, compiled into TweetTokenizer.WORD_RE and applied by TweetTokenizer.tokenize, contains a naked-domain branch whose domain-label prefix [a-z0-9]+(?:[.\-][a-z0-9]+)* is unbounded. Input consisting of many alternating label separators can be partitioned in exponentially many ways, and because the branch also requires a trailing top-level domain that such input never supplies, the engine explores those partitions before failing at each offset. A few kilobytes of input therefore consumes seconds to minutes of single-threaded CPU, and the HANG_RE substitution performed before matching does not collapse the pattern. TweetTokenizer is intended for tokenizing untrusted social-media text, so any service that applies it, or the module-level casual_tokenize, to submitted text can be stalled per request without authentication. Version 3.10.1 bounds the label repetition.

ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the JNG encoder when a blob cannot be opened. Attackers can trigger the memory leak by providing malformed JNG files that fail blob operations, causing resource exhaustion.

OpenEXR is the reference implementation and specification for the EXR image format, widely used in the motion picture industry. In versions 3.1.0 through 3.2.10, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13, an int32_t multiplication in OpenEXRCore's unpack_sample_table() can overflow while decoding a crafted deep tiled EXR file, producing an invalid pointer that leads to a read from an unmapped memory address and a crash. Because the overflow occurs in the standard decoding path (exr_decoding_run), any application that decodes deep tiled EXR files is affected. This issue is fixed in versions 3.2.11, 3.3.13, and 3.4.14.