<?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>Sat, 03 Oct 2026 20:43:54 +0000</lastBuildDate>
    <item>
      <title>BREW-cabal-install-HSEC-2023-0015 — cabal-install uses expired key policies</title>
      <link>https://cve.radiocsirt.org/vuln/brew-cabal-install-hsec-2023-0015</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: cabal-install&lt;/p&gt;
&lt;p&gt;# cabal-install uses expired key policies&lt;/p&gt;
&lt;p&gt;A problem was recently discovered in `cabal-install`&amp;#39;s
implementation of the Hackage Security protocol that would allow an
attacker who was in possession of a revoked private key and who
could perform a man-in-the-middle attack against Hackage to use the
revoked key to deliver malicious packages. At this time, this is
only a theoretical attack - no keys have been revoked. Release
3.10.2.0 of `cabal-install` contains a fix for this bug, and we have
contacted distributors of older versions (such as Linux
distributions) with a patch that they can apply.&lt;/p&gt;
&lt;p&gt;## Background&lt;/p&gt;
&lt;p&gt;Hackage Security is an implementation of [The Update Framework][],
which is a design for a package repository that allows untrusted
mirrors without undermining software supply-chain security. In
particular, Hackage Security cryptographically guarantees the
following properties:&lt;/p&gt;
&lt;p&gt;* Mirrors of Hackage cannot change the contents of packages. This
   prevents the insertion of malicious code.&lt;/p&gt;
&lt;p&gt;* Mirrors cannot omit newer packages for more than a few days
   without clients noticing. This ensures both that mirrors cannot
   maliciously deny security updates, and that mistakes in their
   configuration will be noticed.&lt;/p&gt;
&lt;p&gt;Hackage has a [key policy file][] that delegates authority to a
number of private keys for various purposes. Most of the keys are
kept securely offline by trusted community members who annually
re-sign the various files to indicate that they still have
confide…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Homebrew: cabal-install&lt;/p&gt;
&lt;p&gt;# cabal-install uses expired key policies&lt;/p&gt;
&lt;p&gt;A problem was recently discovered in `cabal-install`&amp;#39;s
implementation of the Hackage Security protocol that would allow an
attacker who was in possession of a revoked private key and who
could perform a man-in-the-middle attack against Hackage to use the
revoked key to deliver malicious packages. At this time, this is
only a theoretical attack - no keys have been revoked. Release
3.10.2.0 of `cabal-install` contains a fix for this bug, and we have
contacted distributors of older versions (such as Linux
distributions) with a patch that they can apply.&lt;/p&gt;
&lt;p&gt;## Background&lt;/p&gt;
&lt;p&gt;Hackage Security is an implementation of [The Update Framework][],
which is a design for a package repository that allows untrusted
mirrors without undermining software supply-chain security. In
particular, Hackage Security cryptographically guarantees the
following properties:&lt;/p&gt;
&lt;p&gt;* Mirrors of Hackage cannot change the contents of packages. This
   prevents the insertion of malicious code.&lt;/p&gt;
&lt;p&gt;* Mirrors cannot omit newer packages for more than a few days
   without clients noticing. This ensures both that mirrors cannot
   maliciously deny security updates, and that mistakes in their
   configuration will be noticed.&lt;/p&gt;
&lt;p&gt;Hackage has a [key policy file][] that delegates authority to a
number of private keys for various purposes. Most of the keys are
kept securely offline by trusted community members who annually
re-sign the various files to indicate that they still have
confide…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/brew-cabal-install-hsec-2023-0015</guid>
    </item>
  </channel>
</rss>
