Vulnerabilities

NVIDIA nvJPEG library contains a vulnerability where an attacker can cause an out-of-bounds read by means of a specially crafted JPEG file. A successful exploit of this vulnerability might lead to information disclosure or denial of service.

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in nvJPEG where a local authenticated user may cause a divide by zero error by submitting a specially crafted JPEG file. A successful exploit of this vulnerability may lead to denial of service.

NVIDIA nvJPEG contains a vulnerability in jpeg encoding where a user may cause an out-of-bounds read by providing a maliciously crafted input image with dimensions that cause integer overflows in array index calculations. A successful exploit of this vulnerability may lead to denial of service.

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in nvJPEG where a local authenticated user may cause a GPU out-of-bounds write by providing certain image dimensions. A successful exploit of this vulnerability may lead to denial of service and information disclosure.

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in nvdisasm where an attacker may cause a heap-based buffer overflow by getting the user to run nvdisasm on a malicious ELF file. A successful exploit of this vulnerability may lead to arbitrary code execution at the privilege level of the user running nvdisasm.

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in the nvdisasm binary where a user may cause an out-of-bounds read by passing a malformed ELF file to nvdisasm. A successful exploit of this vulnerability may lead to a partial denial of service.

NVIDIA CUDA Toolkit for all platforms contains a vulnerability in the cuobjdump binary where a user may cause an out-of-bounds read by passing a malformed ELF file to cuobjdump. A successful exploit of this vulnerability may lead to a partial denial of service.

The Themify Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via several parameters in all versions up to, and including, 7.6.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability was partially patched in version 7.6.9.

nncp before 8.12.0 allows path traversal (for reading or writing) during freqing and file saving via a crafted path in packet data.

A flaw has been found in Magnetism Studios Endurance up to 3.3.0 on macOS. This affects the function loadModuleNamed:WithReply of the file /Applications/Endurance.app/Contents/Library/LaunchServices/com.MagnetismStudios.endurance.helper of the component NSXPC Interface. Executing manipulation can lead to missing authentication. The attack needs to be launched locally. The exploit has been published and may be used.

The MultiLoca - WooCommerce Multi Locations Inventory Management plugin for WordPress is vulnerable to unauthorized modification of data that can lead to privilege escalation due to a missing capability check on the 'wcmlim_settings_ajax_handler' function in all versions up to, and including, 4.2.8. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> Bluetooth: l2cap: Check encryption key size on incoming connection<br /> <br /> This is required for passing GAP/SEC/SEM/BI-04-C PTS test case:<br /> Security Mode 4 Level 4, Responder - Invalid Encryption Key Size<br /> - 128 bit<br /> <br /> This tests the security key with size from 1 to 15 bytes while the<br /> Security Mode 4 Level 4 requests 16 bytes key size.<br /> <br /> Currently PTS fails with the following logs:<br /> - expected:Connection Response:<br /> Code: [3 (0x03)] Code<br /> Identifier: (lt)WildCard: Exists(gt)<br /> Length: [8 (0x0008)]<br /> Destination CID: (lt)WildCard: Exists(gt)<br /> Source CID: [64 (0x0040)]<br /> Result: [3 (0x0003)] Connection refused - Security block<br /> Status: (lt)WildCard: Exists(gt),<br /> but received:Connection Response:<br /> Code: [3 (0x03)] Code<br /> Identifier: [1 (0x01)]<br /> Length: [8 (0x0008)]<br /> Destination CID: [64 (0x0040)]<br /> Source CID: [64 (0x0040)]<br /> Result: [0 (0x0000)] Connection Successful<br /> Status: [0 (0x0000)] No further information available<br /> <br /> And HCI logs:<br /> HCI Event: Command Complete (0x0e) plen 7<br /> Read Encryption Key Size (0x05|0x0008) ncmd 1<br /> Status: Success (0x00)<br /> Handle: 14 Address: 00:1B:DC:F2:24:10 (Vencer Co., Ltd.)<br /> Key size: 7<br /> &gt; ACL Data RX: Handle 14 flags 0x02 dlen 12<br /> L2CAP: Connection Request (0x02) ident 1 len 4<br /> PSM: 4097 (0x1001)<br /> Source CID: 64<br />