<?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>Tue, 06 Oct 2026 17:38:26 +0000</lastBuildDate>
    <item>
      <title>cnvd-2021-20283</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2021-20283</link>
      <description>cnvd-2021-20283</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2021-20283</guid>
    </item>
    <item>
      <title>EUVD-2026-42573</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-42573</link>
      <description>EUVD-2026-42573</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-42573</guid>
    </item>
    <item>
      <title>fkie_cve-2020-14966</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-14966</link>
      <description>&lt;p&gt;An issue was discovered in the jsrsasign package through 8.0.18 for Node.js. It allows a malleability in ECDSA signatures by not checking overflows in the length of a sequence and &amp;#39;0&amp;#39; characters appended or prepended to an integer. The modified signatures are verified as valid. This could have a security-relevant impact if an application relied on a single canonical signature.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An issue was discovered in the jsrsasign package through 8.0.18 for Node.js. It allows a malleability in ECDSA signatures by not checking overflows in the length of a sequence and &amp;#39;0&amp;#39; characters appended or prepended to an integer. The modified signatures are verified as valid. This could have a security-relevant impact if an application relied on a single canonical signature.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-14966</guid>
    </item>
    <item>
      <title>GHSA-p8c3-7rj8-q963 — ECDSA signature validation vulnerability by accepting wrong ASN.1 encoding in jsrsasign</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p8c3-7rj8-q963</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: jsrsasign&lt;/p&gt;
&lt;p&gt;### Impact
Jsrsasign supports ECDSA signature validation which signature value is represented by ASN.1 DER encoding. This vulnerablity may accept a wrong ASN.1 DER encoded ECDSA signature such as:&lt;/p&gt;
&lt;p&gt;- wrong multi-byte ASN.1 length of TLV (ex. 0x820045 even though 0x45 is correct)
- prepending zeros with ASN.1 INTEGER value (ex. 0x00000123 even though 0x0123 is correct)
- appending zeros to signature of ASN.1 TLV (ex. 0x3082....1fbc000000 even though 0x3082....1fbc, appending zeros are ignored.)&lt;/p&gt;
&lt;p&gt;This vulnerability was fixed by strict ASN.1 DER checking.&lt;/p&gt;
&lt;p&gt;Here is an assessment of this vulnerability:&lt;/p&gt;
&lt;p&gt;- If you are not use ECDSA signature validation, this vulnerability is not affected.
- Not ASN.1 format signature like just concatenation of R and S value is not affected such as Bitcoin.
- This vulnerability is affected to all ECC curve parameters.
- Risk to accept a forged or crafted message to be signed is low.
- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.
- ECDSA signatures semantically the same to valid one may be accepted as valid. There are many malleable variants.&lt;/p&gt;
&lt;p&gt;As discussed [here](https://crypto.stackexchange.com/questions/24862/ber-or-der-x9-62-for-ecdsa-signature), there is no standards like X9.62 which requires ASN.1 DER. So ASN.1 BER can be applied to ECDSA however most of implementations like OpenSSL do strict ASN.1 DER checking.&lt;/p&gt;
&lt;p&gt;### Patches
Users using ECDSA signature validation should upgrade to 8.0.19.&lt;/p&gt;
&lt;p&gt;### Workarounds
Do str…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: jsrsasign&lt;/p&gt;
&lt;p&gt;### Impact
Jsrsasign supports ECDSA signature validation which signature value is represented by ASN.1 DER encoding. This vulnerablity may accept a wrong ASN.1 DER encoded ECDSA signature such as:&lt;/p&gt;
&lt;p&gt;- wrong multi-byte ASN.1 length of TLV (ex. 0x820045 even though 0x45 is correct)
- prepending zeros with ASN.1 INTEGER value (ex. 0x00000123 even though 0x0123 is correct)
- appending zeros to signature of ASN.1 TLV (ex. 0x3082....1fbc000000 even though 0x3082....1fbc, appending zeros are ignored.)&lt;/p&gt;
&lt;p&gt;This vulnerability was fixed by strict ASN.1 DER checking.&lt;/p&gt;
&lt;p&gt;Here is an assessment of this vulnerability:&lt;/p&gt;
&lt;p&gt;- If you are not use ECDSA signature validation, this vulnerability is not affected.
- Not ASN.1 format signature like just concatenation of R and S value is not affected such as Bitcoin.
- This vulnerability is affected to all ECC curve parameters.
- Risk to accept a forged or crafted message to be signed is low.
- Risk to raise memory corruption is low since jsrsasign uses BigInteger class.
- ECDSA signatures semantically the same to valid one may be accepted as valid. There are many malleable variants.&lt;/p&gt;
&lt;p&gt;As discussed [here](https://crypto.stackexchange.com/questions/24862/ber-or-der-x9-62-for-ecdsa-signature), there is no standards like X9.62 which requires ASN.1 DER. So ASN.1 BER can be applied to ECDSA however most of implementations like OpenSSL do strict ASN.1 DER checking.&lt;/p&gt;
&lt;p&gt;### Patches
Users using ECDSA signature validation should upgrade to 8.0.19.&lt;/p&gt;
&lt;p&gt;### Workarounds
Do str…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p8c3-7rj8-q963</guid>
    </item>
    <item>
      <title>gsd-2020-14966</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-14966</link>
      <description>gsd-2020-14966</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-14966</guid>
    </item>
  </channel>
</rss>
