Through the patched CVE-2024-0132 fixing Docker vulnerability (CVE-2024-9348) 17th Oct 2024

Preface: When artificial intelligence gains enough intelligence, do you know what it will say if it knows that software or applications developed by humans have vulnerabilities? He would say “Fxxx”!

Background: Docker Engine is the fundamental containerization engine that runs on servers and manages containers, while Docker Desktop is a developer-focused tool that includes Docker Engine along with additional features to simplify the development and testing of containerized applications on local machines.

Can a Docker container have a desktop?
Overview of Docker Desktop – It provides a straightforward GUI (Graphical User Interface) that lets you manage your containers, applications, and images directly from your machine. Docker Desktop reduces the time spent on complex setups so you can focus on writing code.

Vulnerability details: Docker Desktop before v4.34.3 allows RCE via unsanitized GitHub source link in Build view.

Official announcement: Please refer to the vendor announcement for details – https://www.tenable.com/cve/CVE-2024-9348

CVE-2024-0129 – Path traversal issue discovered in NVIDIA NeMo (16-Oct-2024)

Preface: If successful, a path traversal attack may result in the following risks: Unauthorized data access: An attacker can gain access to sensitive files, such as configuration files, system files, or source code, which may include Credentials, application code and data, and sensitive operating system files.

Background: NVIDIA NeMo™ is an end-to-end platform for developing custom generative AI—including large language models (LLMs), multimodal, vision, and speech AI —anywhere. Deliver enterprise-ready models with precise data curation, cutting-edge customization, retrieval-augmented generation (RAG), and accelerated performance.

Standardized method to save a tarfile containing the checkpoint, config, and any additional artifacts. Implemented via nemo[.]core[.]connectors.

Vulnerability details: NVIDIA NeMo contains a vulnerability in SaveRestoreConnector where a user may cause a path traversal issue via an unsafe .tar file extraction. A successful exploit of this vulnerability may lead to code execution and data tampering.

Official announcement: Please refer to the link for details – https://nvidia.custhelp.com/app/answers/detail/a_id/5580

About AMD-SB-7025 and AMD-SB-3013: Technical research papers provided to AMD (15-Oct-2024)

Preface: Examples of side channel attacks include timing attacks, cache-based attacks, and network traffic analysis. Mitigating side channel attacks involves implementing secure coding practices, employing cryptographic algorithms resistant to side channels, and minimizing timing differences.

Background: Cache side channel attacks can infer the secret information processed by the victim by measuring the victim’s cache usage patterns. While the L1 and L2 caches are core-private, the LLC is shared between cores, so LLC-based attacks can be performed when the victim and attacker are not executing on the same core.

Security Focus:

AMD-SB-7025 – Researchers from Azure® Research, Microsoft® have provided to AMD a paper titled “Principled Microarchitectural Isolation on Cloud CPUs” in which they outline a method for potentially mitigating cache side-channel attacks.

Ref: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-7025.html

AMD-SB-3013 – Researchers from Graz University of Technology, Austria, have reported a way for a malicious hypervisor to monitor performance counters and potentially recover data from a guest VM.

Ref: https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3013.html

CVE-2024-45184: Design weakness found in Exynos, a system-on-chip based on Samsung’s ARM development (October 14, 2024)

Preface: USAT (USIM Application Toolkit) technology is based on the original passive operation mode of the SIM card and adds the new active operation capability of the SIM card, which allows applications and services in the SIM card to actively interact with mobile terminals.

Background: The USAT (USIM Application Toolkit) is a standardized set of commands and protocols that allow mobile applications to interact with the USIM card in 3G and 4G/LTE mobile networks.

USAT use case example:

Mobile Banking: Displays a secure PIN entry screen for transaction verification.

Mobile Payments: Interact with USIM cards for secure payment transactions, authorization and token generation.

Mobile messaging: Receive event notifications for incoming SMS messages or delivery reports.

Vulnerability details: An issue was discovered in Samsung Mobile Processor, Wearable Processor, and Modems with chipset Exynos 9820, 9825, 980, 990, 850, 1080, 2100, 1280, 2200, 1330, 1380, 1480, 2400, 9110, W920, W930, Modem 5123, and Modem 5300. A USAT out-of-bounds write due to a heap buffer overflow can lead to a Denial of Service.

Official announcement: Please refer to the link for details – https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2024-45184/

CVE-2024-47670: ocfs2 – add bounds checking (10-10-2024)

Preface: OCFS2 is a file system. It allows users to store and retrieve data. The data is stored in files that are organized in a hierarchical directory tree. It is a POSIX compliant file system that supports the standard interfaces and the behavioral semantics as spelled out by that specification.

Background: OCFS2 is a useful clustered file system that has many general purpose uses beyond Oracle workloads. Utilizing shared storage, it can be used for many general computing tasks where shared clustered storage is required.

OCFS2 supports 512-4K block size. In addition, there is support 4K-1M range for the Cluster size, which we can also call the allocation unit.

Vulnerability details: In the Linux kernel, the following vulnerability has been resolved: ocfs2: add bounds checking to ocfs2_xattr_find_entry() Add a paranoia check to make sure it doesn’t stray beyond valid memory region containing ocfs2 xattr entries when scanning for a match. It will prevent out-of-bound access in case of crafted images.

Official announcement: Please refer to the link for details –

https://www.tenable.com/cve/CVE-2024-47670

Is Qualcomm CVE-2024-23369 the same as CVE-2022-33278? (9th Oct 2024)

Preface: Security patches can be divided into 2 categories — HLOS (High Level Operating System) and NON-HLOS. The first category is for patches concerning the Android system itself and the Linux kernel, and the other is about code running at much lower levels.

Background: The software image running on the main processor is termed as HLOS. The Snapdragon 8 Gen 1 Chipset, that powered the new Samsung Galaxy S22 series, is one of the quickest and most energy-efficient processors available. Qualcomm is known for making some of the greatest chipsets for Android devices, and their current flagship SoC is the Snapdragon 8 Gen 1. Despite the fact that the chip was unveiled in November 2021, few devices have taken advantage of its capabilities. The MotorolaEdge X30, which was released in December 2021, was the first smartphone to include a Snapdragon 8 Gen 1 processor.

Vulnerability details: Memory corruption when invalid length is provided from HLOS for FRS/UDS request/response buffers.

Official announcement: Please refer to the link for details –

https://docs.qualcomm.com/bundle/publicresource/topics/80-41102-2/page_c_tafDiagUpdate.html

About CVE-2024-33066: Memory corruption while redirecting log file to any file location with any file name, said Qualcomm (8th Oct 2024)

Preface: To redirect the standard error output of a command to a file in the Linux shell, you can use the “2>” operator followed by the name of the file where you want to redirect the stderr. Additionally, you can combine the stderr and stdout streams using the “2>&1” operator if you want to redirect both to the same file.

Background: Qualcomm Snapdragon X65 5G Modem-RF System is the world’s first 10 Gigabit 5G and first 3GPP Release 16 modem-to-antenna solution. It is designed with an upgradable architecture to rapidly commercialize 5G Release 16 and extend 5G in mobile broadband, fixed wireless, industrial IoT and 5G private network applications.

Vulnerability details: Memory corruption while redirecting log file to any file location with any file name.

Official announcement: Please refer to the link for details – https://docs.qualcomm.com/product/publicresources/securitybulletin/october-2024-bulletin.html

CVE-2024-38812: Is it a known design weakness in past or it is a new findings? (7th Oct 2024)

Preface: System-Dependent IDL Preprocessor Variables The following system-dependent preprocessor variables are used in building the IDL compiler. They are all defined in:

dce-root-dir/dce/src/rpc/idl/idl_compiler/sysdep[.]h

AUTO_HEAP_STACK_THRESHOLD defines an estimate for the maximum size of a stack in a server stub. If the IDL compiler estimates that this amount will be exceeded, objects will be allocated via malloc instead of on the stack.

Background: What is dcerpc protocol VMware? DCERPC (Distributed Computing Environment/Remote Procedure Call) with Microsoft extensions (MSRPC) is used to transparently execute functions on remote servers. To facilitate this process, interfaces are defined using an interface definition language (IDL).

Vulnerability details: The vCenter Server contains a heap-overflow vulnerability in the implementation of the DCERPC protocol. A malicious actor with network access to vCenter Server may trigger this vulnerability by sending a specially crafted network packet potentially leading to remote code execution.

Official announcement: Please refer to the link for details –

https://nvd.nist.gov/vuln/detail/CVE-2024-38812

CVE-2024-47561: Apache Avro Java SDK: Arbitrary Code Execution when reading Avro Data (Java SDK)

Preface: Kafka understands only byte arrays. Kafka acts as a Broker to convert and transmit data over the network between producers and consumers. But it need a mechanism to convert data into a format that Kafka, producers and consumers can understand.

Background: Apache Avro is a powerful data serialization framework that provides many useful features. It uses the AVRO file format, which is a compact binary format suitable for evolving data schemas. For example, it supports schema enforcement and schema transformations, which are essential for data integrity and compatibility.

Vulnerability details: Schema parsing in the Java SDK of Apache Avro 1.11.3 and previous versions allows bad actors to execute arbitrary code. Users are recommended to upgrade to version 1.11.4 or 1.12.0, which fix this issue.

Official announcement: Please refer to the link for details – https://lists.apache.org/thread/c2v7mhqnmq0jmbwxqq3r5jbj1xg43h5x

CVE‑2024-0103, CVE-2024-0104 & CVE-2024-0105 Interference from the development of supercomputers and artificial intelligence (3rd Oct 2024)

Preface: OpenAI revealed that the project cost $100 million, took 100 days, and used 25,000 NVIDIA A100 GPUs. Each server equipped with these GPUs uses approximately 6.5 kW, so an estimated 50 GWh of energy is consumed during training.

Background: Parallel processing is a method in computing of running two or more processors (CPUs) to handle separate parts of an overall task. Breaking up different parts of a task among multiple processors will help reduce the amount of time to run a program. GPUs render images more quickly than a CPU because of its parallel processing architecture, which allows it to perform multiple calculations across streams of data simultaneously. The CPU is the brain of the operation, responsible for giving instructions to the rest of the system, including the GPU(s).

NVIDIA CUDA provides a simple C/C++ based interface. The CUDA compiler leverages parallelism built into the CUDA programming model as it compiles your program into code.
CUDA is a parallel computing platform and programming interface model created by Nvidia for the development of software which is used by parallel processors. It serves as an alternative to running simulations on traditional CPUs.

Vulnerability details:

CVE-2024-0123 – NVIDIA CUDA toolkit for Windows and Linux contains a vulnerability in the nvdisasm command line tool where an attacker may cause an improper validation in input issue by tricking the user into running nvdisasm on a malicious ELF file. A successful exploit of this vulnerability may lead to denial of service. (CWE‑1285 – Improper Validation of Specified Index, Position, or Offset in Input)

CVE-2024-0124 – NVIDIA CUDA Toolkit for Windows and Linux contains a vulnerability in the nvdisam command line tool, where a user can cause nvdisasm to read freed memory by running it on a malformed ELF file. A successful exploit of this vulnerability might lead to a limited denial of service. (CWE-416 – Use After Free)

CVE-2024-0125 – NVIDIA CUDA Toolkit for Windows and Linux contains a vulnerability in the nvdisam command line tool, where a user can cause a NULL pointer dereference by running nvdisasm on a malformed ELF file. A successful exploit of this vulnerability might lead to a limited denial of service. (CWE-476 – NULL Pointer Dereference)

Official announcement: Please refer to the vendor announcement for details –

https://nvidia.custhelp.com/app/answers/detail/a_id/5577