<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 19:39:34 +0000</lastBuildDate>
    <item>
      <title>BREW-git-annex-CVE-2017-12976 — git-annex command injection via malicious SSH hostname</title>
      <link>https://vulnerability.circl.lu/vuln/brew-git-annex-cve-2017-12976</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: git-annex&lt;/p&gt;
&lt;p&gt;# *git-annex* command injection via malicious SSH hostname&lt;/p&gt;
&lt;p&gt;*git-annex* was vulnerable to the same class of security hole as
git&amp;#39;s **CVE-2017-1000117**. In several cases, `git-annex` parses a
repository URL, and uses it to generate a `ssh` command, with the
hostname to ssh to coming from the URL. If the hostname it parses is
something like `-eProxyCommand=evil`, this could result in arbitrary
local code execution.&lt;/p&gt;
&lt;p&gt;Some details of URL parsing may prevent the exploit working in some
cases.&lt;/p&gt;
&lt;p&gt;Exploiting this would involve the attacker tricking the victim into
adding a remote something like `ssh://-eProxyCommand=evil/blah`.&lt;/p&gt;
&lt;p&gt;One possible avenue for an attacker that avoids exposing the URL to
the user is to use `initremote` with an SSH remote, so embedding the
URL in the *git-annex* branch. Then the victim would enable it with
`enableremote`.&lt;/p&gt;
&lt;p&gt;This was fixed in version **6.20170818**. Now there&amp;#39;s a `SshHost`
type that is not allowed to start with a dash, and every invocation
of `git-annex` uses a function that takes a `SshHost`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: git-annex&lt;/p&gt;
&lt;p&gt;# *git-annex* command injection via malicious SSH hostname&lt;/p&gt;
&lt;p&gt;*git-annex* was vulnerable to the same class of security hole as
git&amp;#39;s **CVE-2017-1000117**. In several cases, `git-annex` parses a
repository URL, and uses it to generate a `ssh` command, with the
hostname to ssh to coming from the URL. If the hostname it parses is
something like `-eProxyCommand=evil`, this could result in arbitrary
local code execution.&lt;/p&gt;
&lt;p&gt;Some details of URL parsing may prevent the exploit working in some
cases.&lt;/p&gt;
&lt;p&gt;Exploiting this would involve the attacker tricking the victim into
adding a remote something like `ssh://-eProxyCommand=evil/blah`.&lt;/p&gt;
&lt;p&gt;One possible avenue for an attacker that avoids exposing the URL to
the user is to use `initremote` with an SSH remote, so embedding the
URL in the *git-annex* branch. Then the victim would enable it with
`enableremote`.&lt;/p&gt;
&lt;p&gt;This was fixed in version **6.20170818**. Now there&amp;#39;s a `SshHost`
type that is not allowed to start with a dash, and every invocation
of `git-annex` uses a function that takes a `SshHost`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/brew-git-annex-cve-2017-12976</guid>
    </item>
    <item>
      <title>CVE-2017-1000116</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2017-1000116</link>
      <description>&lt;p&gt;Mercurial prior to 4.3 did not adequately sanitize hostnames passed to ssh, leading to possible shell-injection attacks.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Mercurial prior to 4.3 did not adequately sanitize hostnames passed to ssh, leading to possible shell-injection attacks.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2017-1000116</guid>
    </item>
  </channel>
</rss>
