<?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, 09 Oct 2026 19:45:54 +0000</lastBuildDate>
    <item>
      <title>CVE-2019-16782 — Possible Information Leak / Session Hijack Vulnerability in Rack</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2019-16782</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rack&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; rack&lt;/p&gt;
&lt;p&gt;There&amp;#39;s a possible information leak / session hijack vulnerability in Rack (RubyGem rack). This vulnerability is patched in versions 1.6.12 and 2.0.8. Attackers may be able to find and hijack sessions by using timing attacks targeting the session id. Session ids are usually stored and indexed in a database that uses some kind of scheme for speeding up lookups of that session id. By carefully measuring the amount of time it takes to look up a session, an attacker may be able to find a valid session id and hijack the session. The session id itself may be generated randomly, but the way the session is indexed by the backing store does not use a secure comparison.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2019-16782</guid>
    </item>
    <item>
      <title>USN-5253-1 — ruby-rack vulnerabilities</title>
      <link>https://cve.radiocsirt.org/vuln/usn-5253-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: ruby-rack, Ubuntu:Pro:16.04:LTS: ruby-rack, Ubuntu:Pro:18.04:LTS: ruby-rack, Ubuntu:Pro:20.04:LTS: ruby-rack&lt;/p&gt;
&lt;p&gt;It was discovered that Rack insecurely handled session ids. An
unauthenticated remote attacker could possibly use this issue to perform
a timing attack and hijack sessions. (CVE-2019-16782)&lt;/p&gt;
&lt;p&gt;It was discovered that Rack was incorrectly handling cookies during
parsing, not validating them or performing the necessary integrity checks.
An attacker could possibly use this issue to overwrite existing cookie
data and gain control over a remote system&amp;#39;s behaviour. This issue only
affected Ubuntu 14.04 ESM. (CVE-2020-8184)&lt;/p&gt;
&lt;p&gt;It was discovered that Rack was not properly parsing data when processing
multipart POST requests. If a user or automated system were tricked into
sending a specially crafted multipart POST request to an application using
Rack, a remote attacker could possibly use this issue to cause a denial of
service. This issue was only fixed in Ubuntu 14.04 ESM and Ubuntu 16.04
ESM. (CVE-2022-30122)&lt;/p&gt;
&lt;p&gt;It was discovered that Rack was not properly escaping untrusted data when
performing logging operations, which could cause shell escaped sequences
to be written to a terminal. If a user or automated system were tricked
into sending a specially crafted request to an application using Rack, a
remote attacker could possibly use this issue to execute arbitrary code in
the machine running the application. This issue was only fixed in Ubuntu
14.04 ESM and Ubuntu 16.04 ESM. (CVE-2022-30123)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: ruby-rack, Ubuntu:Pro:16.04:LTS: ruby-rack, Ubuntu:Pro:18.04:LTS: ruby-rack, Ubuntu:Pro:20.04:LTS: ruby-rack&lt;/p&gt;
&lt;p&gt;It was discovered that Rack insecurely handled session ids. An
unauthenticated remote attacker could possibly use this issue to perform
a timing attack and hijack sessions. (CVE-2019-16782)&lt;/p&gt;
&lt;p&gt;It was discovered that Rack was incorrectly handling cookies during
parsing, not validating them or performing the necessary integrity checks.
An attacker could possibly use this issue to overwrite existing cookie
data and gain control over a remote system&amp;#39;s behaviour. This issue only
affected Ubuntu 14.04 ESM. (CVE-2020-8184)&lt;/p&gt;
&lt;p&gt;It was discovered that Rack was not properly parsing data when processing
multipart POST requests. If a user or automated system were tricked into
sending a specially crafted multipart POST request to an application using
Rack, a remote attacker could possibly use this issue to cause a denial of
service. This issue was only fixed in Ubuntu 14.04 ESM and Ubuntu 16.04
ESM. (CVE-2022-30122)&lt;/p&gt;
&lt;p&gt;It was discovered that Rack was not properly escaping untrusted data when
performing logging operations, which could cause shell escaped sequences
to be written to a terminal. If a user or automated system were tricked
into sending a specially crafted request to an application using Rack, a
remote attacker could possibly use this issue to execute arbitrary code in
the machine running the application. This issue was only fixed in Ubuntu
14.04 ESM and Ubuntu 16.04 ESM. (CVE-2022-30123)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/usn-5253-1</guid>
    </item>
  </channel>
</rss>
