<?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>Mon, 05 Oct 2026 02:11:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2018-10857</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2018-10857</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; [UNKNOWN] git-annex&lt;/p&gt;
&lt;p&gt;git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; [UNKNOWN] git-annex&lt;/p&gt;
&lt;p&gt;git-annex is vulnerable to a private data exposure and exfiltration attack. It could expose the content of files located outside the git-annex repository, or content from a private web server on localhost or the LAN.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2018-10857</guid>
    </item>
    <item>
      <title>HSEC-2023-0010 — git-annex private data exfiltration to compromised remote</title>
      <link>https://vulnerability.circl.lu/vuln/hsec-2023-0010</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: git-annex&lt;/p&gt;
&lt;p&gt;# *git-annex* private data exfiltration to compromised remote&lt;/p&gt;
&lt;p&gt;Some uses of git-annex were vulnerable to a private data exposure
and exfiltration attack. It could expose the content of files
located outside the *git-annex* repository, or content from a
private web server on localhost or the LAN.  Joey Hess discovered
this attack.&lt;/p&gt;
&lt;p&gt;To perform this attack, the attacker needs to have control over one
of the remotes of the victim&amp;#39;s *git-annex* repository. For example,
they may provide a public *git-annex* repository that the victim
clones. Or, equivalantly, the attacker could have read access to the
victim&amp;#39;s *git-annex* repository or a repository it pushes to, and
some channel to get commits into it (e.g. pull requests).&lt;/p&gt;
&lt;p&gt;These exploits are most likely to succeed when the victim is running
the `git-annex` assistant, or is periodically running `git annex
sync --content`.&lt;/p&gt;
&lt;p&gt;To perform the attack the attacker runs `git-annex addurl --relaxed
file:///etc/passwd` and commits this to the repository in some out
of the way place.  After the victim&amp;#39;s git repository receives that
change, `git-annex` follows the attacker-provided URL to the private
data, which it stores in the *git-annex* repository.  From there it
transfers the content to the remote *git-annex* repository that the
attacker has access to.&lt;/p&gt;
&lt;p&gt;As well as `file:///` URLs, the attacker can use URLs to private web
servers.  The URL can also be one that the attacker controls, that
redirects to a URL that is accessible to the victim…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: git-annex&lt;/p&gt;
&lt;p&gt;# *git-annex* private data exfiltration to compromised remote&lt;/p&gt;
&lt;p&gt;Some uses of git-annex were vulnerable to a private data exposure
and exfiltration attack. It could expose the content of files
located outside the *git-annex* repository, or content from a
private web server on localhost or the LAN.  Joey Hess discovered
this attack.&lt;/p&gt;
&lt;p&gt;To perform this attack, the attacker needs to have control over one
of the remotes of the victim&amp;#39;s *git-annex* repository. For example,
they may provide a public *git-annex* repository that the victim
clones. Or, equivalantly, the attacker could have read access to the
victim&amp;#39;s *git-annex* repository or a repository it pushes to, and
some channel to get commits into it (e.g. pull requests).&lt;/p&gt;
&lt;p&gt;These exploits are most likely to succeed when the victim is running
the `git-annex` assistant, or is periodically running `git annex
sync --content`.&lt;/p&gt;
&lt;p&gt;To perform the attack the attacker runs `git-annex addurl --relaxed
file:///etc/passwd` and commits this to the repository in some out
of the way place.  After the victim&amp;#39;s git repository receives that
change, `git-annex` follows the attacker-provided URL to the private
data, which it stores in the *git-annex* repository.  From there it
transfers the content to the remote *git-annex* repository that the
attacker has access to.&lt;/p&gt;
&lt;p&gt;As well as `file:///` URLs, the attacker can use URLs to private web
servers.  The URL can also be one that the attacker controls, that
redirects to a URL that is accessible to the victim…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/hsec-2023-0010</guid>
    </item>
  </channel>
</rss>
