Shell command execution via unescaped custom output
Published Jul 26, 2024 · Updated Aug 2, 2024
Command injection in Starship 1.0.0 through 1.19.0 allows context-dependent attackers to execute shell commands through custom-command output. The custom module passes command output through map_no_escaping, so Bash interprets backticks or $() sequences when rendering the prompt. Exploitation requires a configured custom command that emits attacker-controlled text, such as a commit message, and runs with the victim's shell privileges.
Summary
What happened
Command injection in Starship 1.0.0 through 1.19.0 allows context-dependent attackers to execute shell commands through custom-command output. The custom module passes command output through map_no_escaping, so Bash interprets backticks or $() sequences when rendering the prompt. Exploitation requires a configured custom command that emits attacker-controlled text, such as a commit message, and runs with the victim's shell privileges.
The record
- CVE
- CVE-2024-41815
- Published
- Jul 26, 2024
- Updated
- Aug 2, 2024
- Vendor
- Starship
- Product
- Starship
- Classifications
- CWE-77, T1059.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=>= 1.0.0, < 1.20.0
- Affected versionversion=1.0.0 <1.20.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Custom-command Git commit message proof of conceptproof of concept · demonstrated
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