<?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>Mon, 05 Oct 2026 17:15:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-4603 — Excessive time spent checking DSA keys and parameters</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-4603</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: Checking excessively long DSA keys or parameters may be very
slow.&lt;/p&gt;
&lt;p&gt;Impact summary: Applications that use the functions EVP_PKEY_param_check()
or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may
experience long delays. Where the key or parameters that are being checked
have been obtained from an untrusted source this may lead to a Denial of
Service.&lt;/p&gt;
&lt;p&gt;The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform
various checks on DSA parameters. Some of those computations take a long time
if the modulus (`p` parameter) is too large.&lt;/p&gt;
&lt;p&gt;Trying to use a very large modulus is slow and OpenSSL will not allow using
public keys with a modulus which is over 10,000 bits in length for signature
verification. However the key and parameter check functions do not limit
the modulus size when performing the checks.&lt;/p&gt;
&lt;p&gt;An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check()
and supplies a key or parameters obtained from an untrusted source could be
vulnerable to a Denial of Service attack.&lt;/p&gt;
&lt;p&gt;These functions are not called by OpenSSL itself on untrusted DSA keys so
only applications that directly call these functions may be vulnerable.&lt;/p&gt;
&lt;p&gt;Also vulnerable are the OpenSSL pkey and pkeyparam command line applications
when using the `-check` option.&lt;/p&gt;
&lt;p&gt;The OpenSSL SSL/TLS implementation is not affected by this issue.&lt;/p&gt;
&lt;p&gt;The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: Checking excessively long DSA keys or parameters may be very
slow.&lt;/p&gt;
&lt;p&gt;Impact summary: Applications that use the functions EVP_PKEY_param_check()
or EVP_PKEY_public_check() to check a DSA public key or DSA parameters may
experience long delays. Where the key or parameters that are being checked
have been obtained from an untrusted source this may lead to a Denial of
Service.&lt;/p&gt;
&lt;p&gt;The functions EVP_PKEY_param_check() or EVP_PKEY_public_check() perform
various checks on DSA parameters. Some of those computations take a long time
if the modulus (`p` parameter) is too large.&lt;/p&gt;
&lt;p&gt;Trying to use a very large modulus is slow and OpenSSL will not allow using
public keys with a modulus which is over 10,000 bits in length for signature
verification. However the key and parameter check functions do not limit
the modulus size when performing the checks.&lt;/p&gt;
&lt;p&gt;An application that calls EVP_PKEY_param_check() or EVP_PKEY_public_check()
and supplies a key or parameters obtained from an untrusted source could be
vulnerable to a Denial of Service attack.&lt;/p&gt;
&lt;p&gt;These functions are not called by OpenSSL itself on untrusted DSA keys so
only applications that directly call these functions may be vulnerable.&lt;/p&gt;
&lt;p&gt;Also vulnerable are the OpenSSL pkey and pkeyparam command line applications
when using the `-check` option.&lt;/p&gt;
&lt;p&gt;The OpenSSL SSL/TLS implementation is not affected by this issue.&lt;/p&gt;
&lt;p&gt;The OpenSSL 3.0 and 3.1 FIPS providers are affected by this issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-4603</guid>
    </item>
  </channel>
</rss>
