<?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, 17 Oct 2026 04:49:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-5627</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5627</link>
      <description>EUVD-2026-5627</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5627</guid>
    </item>
    <item>
      <title>fkie_cve-2024-35231</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-35231</link>
      <description>&lt;p&gt;rack-contrib provides contributed rack middleware and utilities for Rack, a Ruby web server interface. Versions of rack-contrib prior to 2.5.0 are vulnerable to denial of service due to the fact that the user controlled data `profiler_runs` was not constrained to any limitation. This would lead to allocating resources on the server side with no limitation and a potential denial of service by remotely user-controlled data. Version 2.5.0 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;rack-contrib provides contributed rack middleware and utilities for Rack, a Ruby web server interface. Versions of rack-contrib prior to 2.5.0 are vulnerable to denial of service due to the fact that the user controlled data `profiler_runs` was not constrained to any limitation. This would lead to allocating resources on the server side with no limitation and a potential denial of service by remotely user-controlled data. Version 2.5.0 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-35231</guid>
    </item>
    <item>
      <title>GHSA-8c8q-2xw3-j869 — rack-contrib vulnerable to Denial of Service due to the unconstrained value of the incoming "profiler_runs" parameter</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8c8q-2xw3-j869</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: rack-contrib&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The next ruby code is vulnerable to denial of service due to the fact that the user controlled data `profiler_runs` was not contrained to any limitation. Which would lead to allocating resources on the server side with no limitation (CWE-770).&lt;/p&gt;
&lt;p&gt;```ruby
        runs = (request.params[&amp;#39;profiler_runs&amp;#39;] || @times).to_i
        result = @profile.profile do
          runs.times { @app.call(env) }
        end
```&lt;/p&gt;
&lt;p&gt;An exploit as such `curl --fail &amp;#34;http://127.0.0.1:9292/?profiler_runs=9999999999&amp;amp;profile=process_time&amp;#34;` may cause resource exhaution by a remotely controlled value.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Herein the `config.ru` file:&lt;/p&gt;
&lt;p&gt;```ruby
require &amp;#39;rack&amp;#39;
require &amp;#39;rack/contrib&amp;#39;&lt;/p&gt;
&lt;p&gt;use Rack::Profiler # if ENV[&amp;#39;RACK_ENV&amp;#39;] == &amp;#39;development&amp;#39;&lt;/p&gt;
&lt;p&gt;# Define a Rack application
app = lambda do |env|
  # Your application logic goes here
  [200, {}, [&amp;#34;Hello World&amp;#34;]]
end&lt;/p&gt;
&lt;p&gt;# Run the Rack application
run app
```&lt;/p&gt;
&lt;p&gt;A Dockerfile:&lt;/p&gt;
&lt;p&gt;```Dockerfile
# Use the official Ruby image as a base
FROM ruby:latest&lt;/p&gt;
&lt;p&gt;# Set the working directory inside the container
WORKDIR /app&lt;/p&gt;
&lt;p&gt;# Copy the custom config.ru file into the container
COPY config.ru .
COPY Gemfile .&lt;/p&gt;
&lt;p&gt;# Install rack and the gems needed to run the app
RUN bundle install&lt;/p&gt;
&lt;p&gt;# Expose the port that rackup will listen on
EXPOSE 9292&lt;/p&gt;
&lt;p&gt;# Run rackup when the container starts
ENTRYPOINT [&amp;#34;rackup&amp;#34;,&amp;#34;--host&amp;#34;,&amp;#34;0.0.0.0&amp;#34;,&amp;#34;--port&amp;#34;,&amp;#34;9292&amp;#34;]&lt;/p&gt;
&lt;p&gt;# Health check
HEALTHCHECK --interval=3s --timeout=10s --start-period=2s --retries=3 CMD curl --fail http://localhost:9292/ || exit 1&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;A G…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; RubyGems: rack-contrib&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;The next ruby code is vulnerable to denial of service due to the fact that the user controlled data `profiler_runs` was not contrained to any limitation. Which would lead to allocating resources on the server side with no limitation (CWE-770).&lt;/p&gt;
&lt;p&gt;```ruby
        runs = (request.params[&amp;#39;profiler_runs&amp;#39;] || @times).to_i
        result = @profile.profile do
          runs.times { @app.call(env) }
        end
```&lt;/p&gt;
&lt;p&gt;An exploit as such `curl --fail &amp;#34;http://127.0.0.1:9292/?profiler_runs=9999999999&amp;amp;profile=process_time&amp;#34;` may cause resource exhaution by a remotely controlled value.&lt;/p&gt;
&lt;p&gt;### PoC&lt;/p&gt;
&lt;p&gt;Herein the `config.ru` file:&lt;/p&gt;
&lt;p&gt;```ruby
require &amp;#39;rack&amp;#39;
require &amp;#39;rack/contrib&amp;#39;&lt;/p&gt;
&lt;p&gt;use Rack::Profiler # if ENV[&amp;#39;RACK_ENV&amp;#39;] == &amp;#39;development&amp;#39;&lt;/p&gt;
&lt;p&gt;# Define a Rack application
app = lambda do |env|
  # Your application logic goes here
  [200, {}, [&amp;#34;Hello World&amp;#34;]]
end&lt;/p&gt;
&lt;p&gt;# Run the Rack application
run app
```&lt;/p&gt;
&lt;p&gt;A Dockerfile:&lt;/p&gt;
&lt;p&gt;```Dockerfile
# Use the official Ruby image as a base
FROM ruby:latest&lt;/p&gt;
&lt;p&gt;# Set the working directory inside the container
WORKDIR /app&lt;/p&gt;
&lt;p&gt;# Copy the custom config.ru file into the container
COPY config.ru .
COPY Gemfile .&lt;/p&gt;
&lt;p&gt;# Install rack and the gems needed to run the app
RUN bundle install&lt;/p&gt;
&lt;p&gt;# Expose the port that rackup will listen on
EXPOSE 9292&lt;/p&gt;
&lt;p&gt;# Run rackup when the container starts
ENTRYPOINT [&amp;#34;rackup&amp;#34;,&amp;#34;--host&amp;#34;,&amp;#34;0.0.0.0&amp;#34;,&amp;#34;--port&amp;#34;,&amp;#34;9292&amp;#34;]&lt;/p&gt;
&lt;p&gt;# Health check
HEALTHCHECK --interval=3s --timeout=10s --start-period=2s --retries=3 CMD curl --fail http://localhost:9292/ || exit 1&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;
&lt;p&gt;A G…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8c8q-2xw3-j869</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-35231</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35231</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-rack-contrib, Ubuntu:18.04:LTS: ruby-rack-contrib&lt;/p&gt;
&lt;p&gt;rack-contrib provides contributed rack middleware and utilities for Rack, a Ruby web server interface. Versions of rack-contrib prior to 2.5.0 are vulnerable to denial of service due to the fact that the user controlled data `profiler_runs` was not constrained to any limitation. This would lead to allocating resources on the server side with no limitation and a potential denial of service by remotely user-controlled data. Version 2.5.0 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: ruby-rack-contrib, Ubuntu:18.04:LTS: ruby-rack-contrib&lt;/p&gt;
&lt;p&gt;rack-contrib provides contributed rack middleware and utilities for Rack, a Ruby web server interface. Versions of rack-contrib prior to 2.5.0 are vulnerable to denial of service due to the fact that the user controlled data `profiler_runs` was not constrained to any limitation. This would lead to allocating resources on the server side with no limitation and a potential denial of service by remotely user-controlled data. Version 2.5.0 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35231</guid>
    </item>
  </channel>
</rss>
