What is CVE-2024-41815?

CVE-2024-41815 is a high-severity command injection vulnerability in starship (rust), affecting versions >= 1.0.0, <= 1.19.0. It is fixed in 1.20.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

How severe is CVE-2024-41815?

CVE-2024-41815 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of starship are affected by CVE-2024-41815?

starship (rust) versions >= 1.0.0, <= 1.19.0 is affected.

Is there a fix for CVE-2024-41815?

Yes. CVE-2024-41815 is fixed in 1.20.0. Upgrade to this version or later.

Is CVE-2024-41815 exploitable, and should I be worried?

Whether CVE-2024-41815 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-41815 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-41815 in starship

Q: How severe is CVE-2024-41815?

CVE-2024-41815 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of starship are affected by CVE-2024-41815?

starship (rust) versions >= 1.0.0, <= 1.19.0 is affected.

Q: Is there a fix for CVE-2024-41815?

Yes. CVE-2024-41815 is fixed in 1.20.0. Upgrade to this version or later.

Q: Is CVE-2024-41815 exploitable, and should I be worried?

Whether CVE-2024-41815 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-41815 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-41815?

Upgrade starship to 1.20.0 or later.

Summary

Starship vulnerable to shell injection via undocumented, unpredictable shell expansion in custom commands

Description

Starship is a cross-shell prompt. Starting in version 1.0.0 and prior to version 1.20.0, undocumented and unpredictable shell expansion and/or quoting rules make it easily to accidentally cause shell injection when using custom commands with starship in bash. Version 1.20.0 fixes the vulnerability.

PoC

Have some custom command which prints out information from a potentially untrusted/unverified source.

[custom.git_commit_name]
command = 'git show -s --format="%<(25,mtrunc)%s"'
style = "italic"
when = true

Impact

This issue only affects users with custom commands, so the scope is limited, and without knowledge of others' commands, it could be hard to successfully target someone.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

CVE-2024-41815 has a CVSS score of 7.4 (High). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.20.0); upgrading removes the vulnerable code path.

Affected versions

starship (>= 1.0.0, <= 1.19.0)

Security releases

starship → 1.20.0 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade starship to 1.20.0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-41815? CVE-2024-41815 is a high-severity command injection vulnerability in starship (rust), affecting versions >= 1.0.0, <= 1.19.0. It is fixed in 1.20.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
How severe is CVE-2024-41815? CVE-2024-41815 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of starship are affected by CVE-2024-41815? starship (rust) versions >= 1.0.0, <= 1.19.0 is affected.
Is there a fix for CVE-2024-41815? Yes. CVE-2024-41815 is fixed in 1.20.0. Upgrade to this version or later.
Is CVE-2024-41815 exploitable, and should I be worried? Whether CVE-2024-41815 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-41815 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-41815? Upgrade starship to 1.20.0 or later.