<?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>Fri, 02 Oct 2026 20:27:15 +0000</lastBuildDate>
    <item>
      <title>BREW-git-annex-CVE-2014-6274 — git-annex plaintext storage of embedded credentials on encrypted remotes</title>
      <link>https://cve.radiocsirt.org/vuln/brew-git-annex-cve-2014-6274</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: git-annex&lt;/p&gt;
&lt;p&gt;# *git-annex* plaintext storage of embedded credentials on encrypted remotes&lt;/p&gt;
&lt;p&gt;*git-annex* had a bug in the **S3** and **Glacier** remotes where if
`embedcreds=yes` was set, and the remote used `encryption=pubkey` or
`encryption=hybrid`, the embedded AWS credentials were stored in the
Git repository in (effectively) plaintext, not encrypted as they
were supposed to be.&lt;/p&gt;
&lt;p&gt;That means that anyone who gets a copy of the Git repository can
extract the AWS credentials from it.  Which would be bad.&lt;/p&gt;
&lt;p&gt;A remote with this problem cannot be enabled using `git annex
enableremote`. Old versions of *git-annex* will fail with a GPG
error; the current version will fail with a pointer to this web
page.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;If your repository has this problem, chose from one of these
approaches to deal with it:&lt;/p&gt;
&lt;p&gt;1. Change your AWS credentials, so the ones stored in the clear in
   git won&amp;#39;t be used.&lt;/p&gt;
&lt;p&gt;After changing the credentials, make sure you have a fixed
   version of git-annex, and you can then re-embed the new creds
   into the repository, encrypted this time, by setting the
   `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment
   variables, and running `git annex enableremote $remotename
   embedcreds=yes`.&lt;/p&gt;
&lt;p&gt;2. Fix the problem and then remove the history of the *git-annex*
   branch of the repository.&lt;/p&gt;
&lt;p&gt;Make sure you have a fixed version of *git-annex*, and force
   *git-annex* to rewrite the embedded creds, with encryption this
   time, by setting by setting the `AWS_SECRET_ACC…&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* plaintext storage of embedded credentials on encrypted remotes&lt;/p&gt;
&lt;p&gt;*git-annex* had a bug in the **S3** and **Glacier** remotes where if
`embedcreds=yes` was set, and the remote used `encryption=pubkey` or
`encryption=hybrid`, the embedded AWS credentials were stored in the
Git repository in (effectively) plaintext, not encrypted as they
were supposed to be.&lt;/p&gt;
&lt;p&gt;That means that anyone who gets a copy of the Git repository can
extract the AWS credentials from it.  Which would be bad.&lt;/p&gt;
&lt;p&gt;A remote with this problem cannot be enabled using `git annex
enableremote`. Old versions of *git-annex* will fail with a GPG
error; the current version will fail with a pointer to this web
page.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;If your repository has this problem, chose from one of these
approaches to deal with it:&lt;/p&gt;
&lt;p&gt;1. Change your AWS credentials, so the ones stored in the clear in
   git won&amp;#39;t be used.&lt;/p&gt;
&lt;p&gt;After changing the credentials, make sure you have a fixed
   version of git-annex, and you can then re-embed the new creds
   into the repository, encrypted this time, by setting the
   `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment
   variables, and running `git annex enableremote $remotename
   embedcreds=yes`.&lt;/p&gt;
&lt;p&gt;2. Fix the problem and then remove the history of the *git-annex*
   branch of the repository.&lt;/p&gt;
&lt;p&gt;Make sure you have a fixed version of *git-annex*, and force
   *git-annex* to rewrite the embedded creds, with encryption this
   time, by setting by setting the `AWS_SECRET_ACC…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-git-annex-cve-2014-6274</guid>
    </item>
    <item>
      <title>EUVD-2026-246038</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-246038</link>
      <description>EUVD-2026-246038</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-246038</guid>
    </item>
    <item>
      <title>fkie_cve-2014-6274</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2014-6274</link>
      <description>&lt;p&gt;git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes
was set, and the remote used encryption=pubkey or encryption=hybrid,
the embedded AWS credentials were stored in the git repository
in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects git-annex: from 3.20121126 before 5.20140919.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes
was set, and the remote used encryption=pubkey or encryption=hybrid,
the embedded AWS credentials were stored in the git repository
in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects git-annex: from 3.20121126 before 5.20140919.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2014-6274</guid>
    </item>
    <item>
      <title>GHSA-ppj6-rmfj-4vjx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ppj6-rmfj-4vjx</link>
      <description>&lt;p&gt;git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes
was set, and the remote used encryption=pubkey or encryption=hybrid,
the embedded AWS credentials were stored in the git repository
in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects git-annex: from 3.20121126 before 5.20140919.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;git-annex had a bug in the S3 and Glacier remotes where if embedcreds=yes
was set, and the remote used encryption=pubkey or encryption=hybrid,
the embedded AWS credentials were stored in the git repository
in (effectively) plaintext, not encrypted as they were supposed to be. This issue affects git-annex: from 3.20121126 before 5.20140919.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ppj6-rmfj-4vjx</guid>
    </item>
    <item>
      <title>gsd-2014-6274</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2014-6274</link>
      <description>gsd-2014-6274</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2014-6274</guid>
    </item>
    <item>
      <title>HSEC-2023-0013 — git-annex plaintext storage of embedded credentials on encrypted remotes</title>
      <link>https://cve.radiocsirt.org/vuln/hsec-2023-0013</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hackage: git-annex&lt;/p&gt;
&lt;p&gt;# *git-annex* plaintext storage of embedded credentials on encrypted remotes&lt;/p&gt;
&lt;p&gt;*git-annex* had a bug in the **S3** and **Glacier** remotes where if
`embedcreds=yes` was set, and the remote used `encryption=pubkey` or
`encryption=hybrid`, the embedded AWS credentials were stored in the
Git repository in (effectively) plaintext, not encrypted as they
were supposed to be.&lt;/p&gt;
&lt;p&gt;That means that anyone who gets a copy of the Git repository can
extract the AWS credentials from it.  Which would be bad.&lt;/p&gt;
&lt;p&gt;A remote with this problem cannot be enabled using `git annex
enableremote`. Old versions of *git-annex* will fail with a GPG
error; the current version will fail with a pointer to this web
page.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;If your repository has this problem, chose from one of these
approaches to deal with it:&lt;/p&gt;
&lt;p&gt;1. Change your AWS credentials, so the ones stored in the clear in
   git won&amp;#39;t be used.&lt;/p&gt;
&lt;p&gt;After changing the credentials, make sure you have a fixed
   version of git-annex, and you can then re-embed the new creds
   into the repository, encrypted this time, by setting the
   `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment
   variables, and running `git annex enableremote $remotename
   embedcreds=yes`.&lt;/p&gt;
&lt;p&gt;2. Fix the problem and then remove the history of the *git-annex*
   branch of the repository.&lt;/p&gt;
&lt;p&gt;Make sure you have a fixed version of *git-annex*, and force
   *git-annex* to rewrite the embedded creds, with encryption this
   time, by setting by setting the `AWS_SECRET_ACC…&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* plaintext storage of embedded credentials on encrypted remotes&lt;/p&gt;
&lt;p&gt;*git-annex* had a bug in the **S3** and **Glacier** remotes where if
`embedcreds=yes` was set, and the remote used `encryption=pubkey` or
`encryption=hybrid`, the embedded AWS credentials were stored in the
Git repository in (effectively) plaintext, not encrypted as they
were supposed to be.&lt;/p&gt;
&lt;p&gt;That means that anyone who gets a copy of the Git repository can
extract the AWS credentials from it.  Which would be bad.&lt;/p&gt;
&lt;p&gt;A remote with this problem cannot be enabled using `git annex
enableremote`. Old versions of *git-annex* will fail with a GPG
error; the current version will fail with a pointer to this web
page.&lt;/p&gt;
&lt;p&gt;## Remediation&lt;/p&gt;
&lt;p&gt;If your repository has this problem, chose from one of these
approaches to deal with it:&lt;/p&gt;
&lt;p&gt;1. Change your AWS credentials, so the ones stored in the clear in
   git won&amp;#39;t be used.&lt;/p&gt;
&lt;p&gt;After changing the credentials, make sure you have a fixed
   version of git-annex, and you can then re-embed the new creds
   into the repository, encrypted this time, by setting the
   `AWS_SECRET_ACCESS_KEY` and `AWS_ACCESS_KEY_ID` environment
   variables, and running `git annex enableremote $remotename
   embedcreds=yes`.&lt;/p&gt;
&lt;p&gt;2. Fix the problem and then remove the history of the *git-annex*
   branch of the repository.&lt;/p&gt;
&lt;p&gt;Make sure you have a fixed version of *git-annex*, and force
   *git-annex* to rewrite the embedded creds, with encryption this
   time, by setting by setting the `AWS_SECRET_ACC…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/hsec-2023-0013</guid>
    </item>
  </channel>
</rss>
