Openshift Source To Image S2I
Monthly
Symbolic-link traversal during archive unpacking in Red Hat's source-to-image (S2I) tooling lets an attacker who can supply or otherwise influence the builder image consumed by a build create links that resolve to absolute paths outside the extraction directory, allowing file reads or modifications beyond the intended sandbox on the host. The flaw is rated CVSS 3.1 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), so exploitation is not an unauthenticated drive-by: the attacker needs the privileges required to introduce or reference a malicious builder image, and only environments that run S2I builds against untrusted or attacker-influenced images are realistically exposed. The scope is marked Changed because the payload escapes the build container boundary, but confidentiality and integrity impact are each only Low; no public exploit code and no confirmed active exploitation were identified at time of analysis.
Symbolic-link traversal during archive unpacking in Red Hat's source-to-image (S2I) tooling lets an attacker who can supply or otherwise influence the builder image consumed by a build create links that resolve to absolute paths outside the extraction directory, allowing file reads or modifications beyond the intended sandbox on the host. The flaw is rated CVSS 3.1 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N), so exploitation is not an unauthenticated drive-by: the attacker needs the privileges required to introduce or reference a malicious builder image, and only environments that run S2I builds against untrusted or attacker-influenced images are realistically exposed. The scope is marked Changed because the payload escapes the build container boundary, but confidentiality and integrity impact are each only Low; no public exploit code and no confirmed active exploitation were identified at time of analysis.