Mitigation Strategies

To mitigate this vulnerability, upgrade kaniko to version 1.25.10 or later, as this version uses securejoin for path resolution in tar extraction, preventing path traversal attacks.

Useful 0 Not Useful 0

Executive Summary

This vulnerability exists in kaniko versions starting from 1.25.4 up to but not including 1.25.10. Kaniko unpacks build context archives using a method that does not ensure the extracted files remain within the intended destination directory. Specifically, it uses filepath.Join(dest, cleanedName) without enforcing path restrictions, allowing a tar entry like "../outside.txt" to escape the extraction root and write files outside the destination directory.

In environments where registry authentication is used, this flaw can be exploited in combination with docker credential helpers to achieve code execution within the executor process. The issue was fixed in version 1.25.10 by using a secure path resolution method called securejoin during tar extraction.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to unauthorized code execution within the kaniko executor process. An attacker can exploit the path traversal flaw to write files outside the intended directory, potentially overwriting critical files or injecting malicious code.

In environments using registry authentication, this can be chained with docker credential helpers to escalate the impact, allowing an attacker to execute arbitrary code, which can compromise the security and integrity of the build environment.

Useful 0 Not Useful 0

Compliance Impact

I don't know

Useful 0 Not Useful 0

Detection Guidance

I don't know

Useful 0 Not Useful 0