Code execution via executable-path validation
Published Sep 8, 2022 · Updated Sep 17, 2024
Code injection in Google Jib Core before 0.22.0 allows remote attackers to execute an attacker-selected program through a crafted executable path. CliDockerClient.isDockerInstalled passes the supplied dockerExecutable path directly to ProcessBuilder.start instead of checking the path, causing the validation call itself to launch that file. Exploitation requires a consuming application to pass attacker-controlled path input into this library API; execution occurs with the application's privileges.
Summary
What happened
Code injection in Google Jib Core before 0.22.0 allows remote attackers to execute an attacker-selected program through a crafted executable path. CliDockerClient.isDockerInstalled passes the supplied dockerExecutable path directly to ProcessBuilder.start instead of checking the path, causing the validation call itself to launch that file. Exploitation requires a consuming application to pass attacker-controlled path input into this library API; execution occurs with the application's privileges.
The record
- CVE
- CVE-2022-25914
- Published
- Sep 8, 2022
- Updated
- Sep 17, 2024
- Vendor
- Product
- Jib Core
- Classifications
- T1106
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2022CVE publishedPublication date reported by the CVE source.
- Sep 17, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <0.22.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Snyk isDockerInstalled proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo