<?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>Wed, 30 Sep 2026 02:03:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-42770 — FFC-DH Peer Validation Uses Attacker-Supplied q</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-42770</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; OpenSSL&lt;/p&gt;
&lt;p&gt;Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42)
peer key, the peer key is not properly checked for the subgroup membership.&lt;/p&gt;
&lt;p&gt;Impact summary: A malicious peer which presents an X9.42 key carrying the
victim&amp;#39;s p and g parameters, a forged q = r (a small prime factor of the
cofactor (p−1)/q_local), and a public value Y of order r can recover the
victim&amp;#39;s private key after a small number of key exchange attempts.&lt;/p&gt;
&lt;p&gt;When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the
subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer&amp;#39;s
own q parameter, not the local key&amp;#39;s q. The peer&amp;#39;s domain parameters are
then matched against the domain parameters of the private key, but the value
of q is not compared.&lt;/p&gt;
&lt;p&gt;A malicious peer who presents an X9.42 key carrying the victim&amp;#39;s p, g,
a forged q = r (a small prime factor of the cofactor), and a public
value Y of order r passes all checks. The shared secret then takes only
r distinct values, leaking priv mod r. Repeating for each small-prime
factor of the cofactor and combining via CRT recovers the full private
key (Lim–Lee / small-subgroup-confinement attack).&lt;/p&gt;
&lt;p&gt;The realistic attack surface is narrow: principally CMP deployments with
long-lived RA/CA DHX keys and bespoke enterprise or government applications
using X9.42 DHX static keys with interactive protocols and therefore this
issue was assigned Low severity.&lt;/p&gt;
&lt;p&gt;The FIPS modules in 4.0, 3.6, 3.5, 3.4, 3.1.2 and 3.0 are affected by this
i…&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: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42)
peer key, the peer key is not properly checked for the subgroup membership.&lt;/p&gt;
&lt;p&gt;Impact summary: A malicious peer which presents an X9.42 key carrying the
victim&amp;#39;s p and g parameters, a forged q = r (a small prime factor of the
cofactor (p−1)/q_local), and a public value Y of order r can recover the
victim&amp;#39;s private key after a small number of key exchange attempts.&lt;/p&gt;
&lt;p&gt;When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the
subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer&amp;#39;s
own q parameter, not the local key&amp;#39;s q. The peer&amp;#39;s domain parameters are
then matched against the domain parameters of the private key, but the value
of q is not compared.&lt;/p&gt;
&lt;p&gt;A malicious peer who presents an X9.42 key carrying the victim&amp;#39;s p, g,
a forged q = r (a small prime factor of the cofactor), and a public
value Y of order r passes all checks. The shared secret then takes only
r distinct values, leaking priv mod r. Repeating for each small-prime
factor of the cofactor and combining via CRT recovers the full private
key (Lim–Lee / small-subgroup-confinement attack).&lt;/p&gt;
&lt;p&gt;The realistic attack surface is narrow: principally CMP deployments with
long-lived RA/CA DHX keys and bespoke enterprise or government applications
using X9.42 DHX static keys with interactive protocols and therefore this
issue was assigned Low severity.&lt;/p&gt;
&lt;p&gt;The FIPS modules in 4.0, 3.6, 3.5, 3.4, 3.1.2 and 3.0 are affected by this
i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-42770</guid>
    </item>
  </channel>
</rss>
