<?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 19:43:05 +0000</lastBuildDate>
    <item>
      <title>bdu:2022-06098</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2022-06098</link>
      <description>bdu:2022-06098</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2022-06098</guid>
    </item>
    <item>
      <title>BIT-modsecurity-2020-15598</title>
      <link>https://cve.radiocsirt.org/vuln/bit-modsecurity-2020-15598</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: modsecurity&lt;/p&gt;
&lt;p&gt;Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Bitnami: modsecurity&lt;/p&gt;
&lt;p&gt;Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bit-modsecurity-2020-15598</guid>
    </item>
    <item>
      <title>EUVD-2026-43048</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-43048</link>
      <description>EUVD-2026-43048</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-43048</guid>
    </item>
    <item>
      <title>fkie_cve-2020-15598</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-15598</link>
      <description>&lt;p&gt;Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-15598</guid>
    </item>
    <item>
      <title>GHSA-ff2c-wgr6-2p58</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ff2c-wgr6-2p58</link>
      <description>&lt;p&gt;** DISPUTED ** Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;** DISPUTED ** Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ff2c-wgr6-2p58</guid>
    </item>
    <item>
      <title>gsd-2020-15598</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-15598</link>
      <description>gsd-2020-15598</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-15598</guid>
    </item>
    <item>
      <title>openSUSE-SU-2023:0257-1 — Security update for modsecurity</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2023:0257-1</link>
      <description>&lt;p&gt;Security update for modsecurity&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for modsecurity&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2023:0257-1</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2020-15598</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15598</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: modsecurity&lt;/p&gt;
&lt;p&gt;** DISPUTED ** Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: modsecurity&lt;/p&gt;
&lt;p&gt;** DISPUTED ** Trustwave ModSecurity 3.x through 3.0.4 allows denial of service via a special request. NOTE: The discoverer reports &amp;#34;Trustwave has signaled they are disputing our claims.&amp;#34; The CVE suggests that there is a security issue with how ModSecurity handles regular expressions that can result in a Denial of Service condition. The vendor does not consider this as a security issue because1) there is no default configuration issue here. An attacker would need to know that a rule using a potentially problematic regular expression was in place, 2) the attacker would need to know the basic nature of the regular expression itself to exploit any resource issues. It&amp;#39;s well known that regular expression usage can be taxing on system resources regardless of the use case. It is up to the administrator to decide on when it is appropriate to trade resources for potential security benefit.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-15598</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-1579 — Trustwave ModSecurity: Schwachstelle ermöglicht Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1579</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Trustwave ModSecurity und NGINX Plus ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Trustwave ModSecurity und NGINX Plus ausnutzen, um einen Denial of Service Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1579</guid>
    </item>
  </channel>
</rss>
