Threat Intelligence Database

Kedro version 1.2.0 contains a path traversal vulnerability in the _get_versioned_path() method, which unsafely incorporates user-supplied version strings into filesystem paths. This flaw also affects the CLI via the --load-versions parameter, allowing crafted input to escape intended directories. Exploitation can lead to unauthorized file reads and cross-project data access.

Kedro versions prior to 1.3.0 contain a critical remote code execution vulnerability due to unsafe loading of a logging configuration file specified by the KEDRO_LOGGING_CONFIG environment variable. The logging configuration supports a special key that allows arbitrary callable instantiation, enabling attackers to execute system commands during application startup. This vulnerability is fixed in Kedro version 1.3.0.

Kedro versions prior to 1.3.0 contain a path traversal vulnerability in the _get_versioned_path() method, which improperly handles user-supplied version strings. This allows an attacker who can control the version string to cause Kedro to load files outside the intended versioned dataset directory. The issue affects multiple entry points including catalog.load, DataCatalog.from_config, and the CLI. This vulnerability can lead to unauthorized file reads, data poisoning, or cross-tenant data access in shared environments. The vulnerability is fixed in Kedro version 1.3.

A Remote Code Execution (RCE) vulnerability has been identified in the Kedro ShelveStore class (version 0.19.8). This vulnerability allows an attacker to execute arbitrary Python code via deserialization of malicious payloads, potentially leading to a full system compromise. The ShelveStore class uses Python's shelve module to manage session data, which relies on pickle for serialization. Crafting a malicious payload and storing it in the shelve file can lead to RCE when the payload is deserialized.

In kedro-org/kedro version 0.19.8, the `pull_package()` API function allows users to download and extract micro packages from the Internet. However, the function `project_wheel_metadata()` within the code path can execute the `setup.py` file inside the tar file, leading to remote code execution (RCE) by running arbitrary commands on the victim's machine.

HighVulnerabilityGermanyFranceUnited Kingdom+7#cve#cve-2024-12215#cwe-94