<?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 15:46:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-38037</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-38037</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rails ActiveSupport&lt;/p&gt;
&lt;p&gt;ActiveSupport::EncryptedFile writes contents that will be encrypted to a&#13;
temporary file.  The temporary file&amp;#39;s permissions are defaulted to the user&amp;#39;s&#13;
current `umask` settings, meaning that it&amp;#39;s possible for other users on the&#13;
same system to read the contents of the temporary file.&#13;
&#13;
Attackers that have access to the file system could possibly read the contents&#13;
of this temporary file while a user is editing it.&#13;
&#13;
All users running an affected release should either upgrade or use one of the&#13;
workarounds immediately.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Rails ActiveSupport&lt;/p&gt;
&lt;p&gt;ActiveSupport::EncryptedFile writes contents that will be encrypted to a&#13;
temporary file.  The temporary file&amp;#39;s permissions are defaulted to the user&amp;#39;s&#13;
current `umask` settings, meaning that it&amp;#39;s possible for other users on the&#13;
same system to read the contents of the temporary file.&#13;
&#13;
Attackers that have access to the file system could possibly read the contents&#13;
of this temporary file while a user is editing it.&#13;
&#13;
All users running an affected release should either upgrade or use one of the&#13;
workarounds immediately.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-38037</guid>
    </item>
    <item>
      <title>GHSA-cr5q-6q9f-rq6q — Active Support Possibly Discloses Locally Encrypted Files</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-cr5q-6q9f-rq6q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: activesupport&lt;/p&gt;
&lt;p&gt;There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.&lt;/p&gt;
&lt;p&gt;Versions Affected: &amp;gt;= 5.2.0 Not affected: &amp;lt; 5.2.0 Fixed Versions: 7.0.7.1, 6.1.7.5&lt;/p&gt;
&lt;p&gt;# Impact
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file’s permissions are defaulted to the user’s current umask settings, meaning that it’s possible for other users on the same system to read the contents of the temporary file.&lt;/p&gt;
&lt;p&gt;Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.&lt;/p&gt;
&lt;p&gt;All users running an affected release should either upgrade or use one of the workarounds immediately.&lt;/p&gt;
&lt;p&gt;# Releases
The fixed releases are available at the normal locations.&lt;/p&gt;
&lt;p&gt;# Workarounds
To work around this issue, you can set your umask to be more restrictive like this:&lt;/p&gt;
&lt;p&gt;```ruby
$ umask 0077
```&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: activesupport&lt;/p&gt;
&lt;p&gt;There is a possible file disclosure of locally encrypted files in Active Support. This vulnerability has been assigned the CVE identifier CVE-2023-38037.&lt;/p&gt;
&lt;p&gt;Versions Affected: &amp;gt;= 5.2.0 Not affected: &amp;lt; 5.2.0 Fixed Versions: 7.0.7.1, 6.1.7.5&lt;/p&gt;
&lt;p&gt;# Impact
ActiveSupport::EncryptedFile writes contents that will be encrypted to a temporary file. The temporary file’s permissions are defaulted to the user’s current umask settings, meaning that it’s possible for other users on the same system to read the contents of the temporary file.&lt;/p&gt;
&lt;p&gt;Attackers that have access to the file system could possibly read the contents of this temporary file while a user is editing it.&lt;/p&gt;
&lt;p&gt;All users running an affected release should either upgrade or use one of the workarounds immediately.&lt;/p&gt;
&lt;p&gt;# Releases
The fixed releases are available at the normal locations.&lt;/p&gt;
&lt;p&gt;# Workarounds
To work around this issue, you can set your umask to be more restrictive like this:&lt;/p&gt;
&lt;p&gt;```ruby
$ umask 0077
```&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-cr5q-6q9f-rq6q</guid>
    </item>
  </channel>
</rss>
