|
Lines 1-3
Link Here
|
|
|
1 |
<vuln vid="972ba0e8-8b8a-11ec-b369-6c3be5272acd"> |
| 2 |
<topic>Node.js -- January 2022 Security Releases</topic> |
| 3 |
<affects> |
| 4 |
<package> |
| 5 |
<name>node</name> |
| 6 |
<range><ge>12.0.0</ge><lt>12.22.9</lt></range> |
| 7 |
<range><ge>14.0.0</ge><lt>14.18.3</lt></range> |
| 8 |
<range><ge>16.0.0</ge><lt>16.13.2</lt></range> |
| 9 |
<range><ge>17.0.0</ge><lt>17.3.1</lt></range> |
| 10 |
</package> |
| 11 |
<package> |
| 12 |
<name>node16</name> |
| 13 |
<range><lt>16.13.2</lt></range> |
| 14 |
</package> |
| 15 |
<package> |
| 16 |
<name>node14</name> |
| 17 |
<range><lt>14.18.3</lt></range> |
| 18 |
</package> |
| 19 |
</affects> |
| 20 |
<description> |
| 21 |
<body xmlns="http://www.w3.org/1999/xhtml"> |
| 22 |
<p>Node.js reports:</p> |
| 23 |
<blockquote cite="https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/"> |
| 24 |
<h1>Improper handling of URI Subject Alternative Names (Medium)(CVE-2021-44531)</h1> |
| 25 |
<p>Accepting arbitrary Subject Alternative Name (SAN) types, unless a PKI is specifically defined to use a particular SAN type, can result in bypassing name-constrained intermediates. Node.js was accepting URI SAN types, which PKIs are often not defined to use. Additionally, when a protocol allows URI SANs, Node.js did not match the URI correctly.</p> |
| 26 |
<h1>Certificate Verification Bypass via String Injection (Medium)(CVE-2021-44532)</h1> |
| 27 |
<p>Node.js converts SANs (Subject Alternative Names) to a string format. It uses this string to check peer certificates against hostnames when validating connections. The string format was subject to an injection vulnerability when name constraints were used within a certificate chain, allowing the bypass of these name constraints.</p> |
| 28 |
<h1>Incorrect handling of certificate subject and issuer fields (Medium)(CVE-2021-44533)</h1> |
| 29 |
<p>Node.js did not handle multi-value Relative Distinguished Names correctly. Attackers could craft certificate subjects containing a single-value Relative Distinguished Name that would be interpreted as a multi-value Relative Distinguished Name, for example, in order to inject a Common Name that would allow bypassing the certificate subject verification.</p> |
| 30 |
<h1>Prototype pollution via <code>console.table</code> properties (Low)(CVE-2022-21824)</h1> |
| 31 |
<p>Due to the formatting logic of the <code>console.table()</code> function it was not safe to allow user controlled input to be passed to the <code>properties</code> parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be <code>__proto__</code>. The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.</p> |
| 32 |
</blockquote> |
| 33 |
</body> |
| 34 |
</description> |
| 35 |
<references> |
| 36 |
<cvename>CVE-2021-44531</cvename> |
| 37 |
<cvename>CVE-2021-44532</cvename> |
| 38 |
<cvename>CVE-2021-44533</cvename> |
| 39 |
<cvename>CVE-2022-21824</cvename> |
| 40 |
<url>https://nodejs.org/en/blog/vulnerability/jan-2022-security-releases/</url> |
| 41 |
</references> |
| 42 |
<dates> |
| 43 |
<discovery>2022-01-10</discovery> |
| 44 |
<entry>2022-02-12</entry> |
| 45 |
</dates> |
| 46 |
</vuln> |
| 47 |
|
| 1 |
<vuln vid="0b0ad196-1ee8-4a98-89b1-4d5d82af49a9"> |
48 |
<vuln vid="0b0ad196-1ee8-4a98-89b1-4d5d82af49a9"> |
| 2 |
<topic>jenkins -- DoS vulnerability in bundled XStream library</topic> |
49 |
<topic>jenkins -- DoS vulnerability in bundled XStream library</topic> |
| 3 |
<affects> |
50 |
<affects> |