<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 15 Oct 2026 17:00:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41815 — Starship vulnerable to shell injection via undocumented, unpredictable shell expansion in custom commands</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-41815</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; starship&lt;/p&gt;
&lt;p&gt;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. This issue only affects users with custom commands, so the scope is limited, and without knowledge of others&amp;#39; commands, it could be hard to successfully target someone. Version 1.20.0 fixes the vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; starship&lt;/p&gt;
&lt;p&gt;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. This issue only affects users with custom commands, so the scope is limited, and without knowledge of others&amp;#39; commands, it could be hard to successfully target someone. Version 1.20.0 fixes the vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-41815</guid>
    </item>
    <item>
      <title>RUSTSEC-2024-0446 — Shell expansion in custom commands</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2024-0446</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: starship&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;I wanted to show the git commit name in my prompt (I use bash), so I added a command:&lt;/p&gt;
&lt;p&gt;```
[custom.git_commit_name]
command = &amp;#39;git show -s --format=&amp;#34;%&amp;lt;(25,mtrunc)%s&amp;#34;&amp;#39;
style = &amp;#34;italic&amp;#34;
when = true
```&lt;/p&gt;
&lt;p&gt;To my surprise, when I had a commit with backticks in it,
the backticks were expanded. e.g.:&lt;/p&gt;
&lt;p&gt;```
touch foo
git add foo
git commit -m &amp;#39;`ls`&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Thankfully I noticed it on my own commit before checking out
someone&amp;#39;s code whose commit message was&lt;/p&gt;
&lt;p&gt;`rm -rf /important/stuff`&lt;/p&gt;
&lt;p&gt;The documentation says:&lt;/p&gt;
&lt;p&gt;Command output is printed unescaped to the prompt&lt;/p&gt;
&lt;p&gt;```
    Whatever output the command generates is printed unmodified in the prompt.
    This means if the output contains special sequences that are interpreted
    by your shell they will be expanded when displayed. These special
    sequences are shell specific, e.g. you can write a command module that
    writes bash sequences, e.g. \h, but this module will not work in a fish
    or zsh shell.&lt;/p&gt;
&lt;p&gt;Format strings can also contain shell specific prompt sequences, e.g. Bash, Zsh.
```&lt;/p&gt;
&lt;p&gt;However, it doesn&amp;#39;t specifically mention shell injection with $()
and backticks; it just mentions the prompt escape sequences, and
the link doesn&amp;#39;t suggest any shell injection possibilities either.&lt;/p&gt;
&lt;p&gt;Furthermore, I can&amp;#39;t even figure out how to properly escape th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: starship&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;I wanted to show the git commit name in my prompt (I use bash), so I added a command:&lt;/p&gt;
&lt;p&gt;```
[custom.git_commit_name]
command = &amp;#39;git show -s --format=&amp;#34;%&amp;lt;(25,mtrunc)%s&amp;#34;&amp;#39;
style = &amp;#34;italic&amp;#34;
when = true
```&lt;/p&gt;
&lt;p&gt;To my surprise, when I had a commit with backticks in it,
the backticks were expanded. e.g.:&lt;/p&gt;
&lt;p&gt;```
touch foo
git add foo
git commit -m &amp;#39;`ls`&amp;#39;
```&lt;/p&gt;
&lt;p&gt;Thankfully I noticed it on my own commit before checking out
someone&amp;#39;s code whose commit message was&lt;/p&gt;
&lt;p&gt;`rm -rf /important/stuff`&lt;/p&gt;
&lt;p&gt;The documentation says:&lt;/p&gt;
&lt;p&gt;Command output is printed unescaped to the prompt&lt;/p&gt;
&lt;p&gt;```
    Whatever output the command generates is printed unmodified in the prompt.
    This means if the output contains special sequences that are interpreted
    by your shell they will be expanded when displayed. These special
    sequences are shell specific, e.g. you can write a command module that
    writes bash sequences, e.g. \h, but this module will not work in a fish
    or zsh shell.&lt;/p&gt;
&lt;p&gt;Format strings can also contain shell specific prompt sequences, e.g. Bash, Zsh.
```&lt;/p&gt;
&lt;p&gt;However, it doesn&amp;#39;t specifically mention shell injection with $()
and backticks; it just mentions the prompt escape sequences, and
the link doesn&amp;#39;t suggest any shell injection possibilities either.&lt;/p&gt;
&lt;p&gt;Furthermore, I can&amp;#39;t even figure out how to properly escape th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2024-0446</guid>
    </item>
  </channel>
</rss>
