<?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 06:27:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-221554</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-221554</link>
      <description>EUVD-2026-221554</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-221554</guid>
    </item>
    <item>
      <title>fkie_cve-2023-25653</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-25653</link>
      <description>&lt;p&gt;node-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for web browsers and node.js-based servers. Prior to version 2.2.0, when using the non-default &amp;#34;fallback&amp;#34; crypto back-end, ECC operations in `node-jose` can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation.  For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input. The issue has been patched in version 2.2.0. Since this issue is only present in the &amp;#34;fallback&amp;#34; crypto implementation, it can be avoided by ensuring that either WebCrypto or the Node `crypto` module is available in the JS environment where `node-jose` is being run.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;node-jose is a JavaScript implementation of the JSON Object Signing and Encryption (JOSE) for web browsers and node.js-based servers. Prior to version 2.2.0, when using the non-default &amp;#34;fallback&amp;#34; crypto back-end, ECC operations in `node-jose` can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation.  For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input. The issue has been patched in version 2.2.0. Since this issue is only present in the &amp;#34;fallback&amp;#34; crypto implementation, it can be avoided by ensuring that either WebCrypto or the Node `crypto` module is available in the JS environment where `node-jose` is being run.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-25653</guid>
    </item>
    <item>
      <title>GHSA-5h4j-qrvg-9xhw — Improper calculations in ECC implementation can trigger a Denial-of-Service (DoS)</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5h4j-qrvg-9xhw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-jose&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;When using the non-default &amp;#34;fallback&amp;#34; crypto back-end, ECC operations in `node-jose` can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation.  For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input.&lt;/p&gt;
&lt;p&gt;#### Technical summary&lt;/p&gt;
&lt;p&gt;The JOSE logic implemented by `node-jose` usually relies on an external cryptographic library for the underlying cryptographic primitives that JOSE operations require.  When WebCrypto or the Node `crypto` module are available, they are used.  When neither of these libraries is available, `node-jose` includes its own &amp;#34;fallback&amp;#34; implementations of some algorithms based on `node-forge`, in particular implementations of ECDH and ECDSA.&lt;/p&gt;
&lt;p&gt;A various points, these algorithm implementations need to compute to the X coordinate of an elliptic curve point.  This is done by calling the `getX()` method of the object representing the point, which is an alias of the function `pointFpGetX()` in `lib/deps/ecc/math.js`.&lt;/p&gt;
&lt;p&gt;Computing the X coordinate from the form in which the point is stored requires computing the modular inverse of the Z coordinate, using the `modInverse` function from the `jsbn` library (e.g., `this.z.modInverse(this.curve.p)`).  The output of this function call is multiplied by another value before being reduced with the `barrettReduce()` function.&lt;/p&gt;
&lt;p&gt;The root cause of this issue is that the `jsbn` `modInverse` function sometimes r…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: node-jose&lt;/p&gt;
&lt;p&gt;### Description&lt;/p&gt;
&lt;p&gt;When using the non-default &amp;#34;fallback&amp;#34; crypto back-end, ECC operations in `node-jose` can trigger a Denial-of-Service (DoS) condition, due to a possible infinite loop in an internal calculation.  For some ECC operations, this condition is triggered randomly; for others, it can be triggered by malicious input.&lt;/p&gt;
&lt;p&gt;#### Technical summary&lt;/p&gt;
&lt;p&gt;The JOSE logic implemented by `node-jose` usually relies on an external cryptographic library for the underlying cryptographic primitives that JOSE operations require.  When WebCrypto or the Node `crypto` module are available, they are used.  When neither of these libraries is available, `node-jose` includes its own &amp;#34;fallback&amp;#34; implementations of some algorithms based on `node-forge`, in particular implementations of ECDH and ECDSA.&lt;/p&gt;
&lt;p&gt;A various points, these algorithm implementations need to compute to the X coordinate of an elliptic curve point.  This is done by calling the `getX()` method of the object representing the point, which is an alias of the function `pointFpGetX()` in `lib/deps/ecc/math.js`.&lt;/p&gt;
&lt;p&gt;Computing the X coordinate from the form in which the point is stored requires computing the modular inverse of the Z coordinate, using the `modInverse` function from the `jsbn` library (e.g., `this.z.modInverse(this.curve.p)`).  The output of this function call is multiplied by another value before being reduced with the `barrettReduce()` function.&lt;/p&gt;
&lt;p&gt;The root cause of this issue is that the `jsbn` `modInverse` function sometimes r…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5h4j-qrvg-9xhw</guid>
    </item>
    <item>
      <title>gsd-2023-25653</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-25653</link>
      <description>gsd-2023-25653</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-25653</guid>
    </item>
  </channel>
</rss>
