Node.js < 12.22.9, < 14.18.3, < 16.13.2, and < 17.3.1 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.Affected versions of Node.js that do not accept multi-value Relative Distinguished Names and are thus not vulnerable to such attacks themselves. However, third-party code that uses node's ambiguous presentation of certificate subjects may be vulnerable.
{
"versions": [
{
"introduced": "0"
},
{
"last_affected": "20.3.5"
},
{
"introduced": "0"
},
{
"last_affected": "21.3.1"
},
{
"introduced": "0"
},
{
"last_affected": "22.0.0.2"
}
]
}{
"versions": [
{
"introduced": "0"
},
{
"fixed": "8.0.29"
},
{
"introduced": "0"
},
{
"last_affected": "8.0.29"
},
{
"introduced": "0"
},
{
"last_affected": "8.0.28"
},
{
"introduced": "0"
},
{
"last_affected": "8.0.29"
},
{
"introduced": "0"
},
{
"last_affected": "5.7.37"
},
{
"introduced": "8.0.0"
},
{
"last_affected": "8.0.28"
},
{
"introduced": "0"
},
{
"last_affected": "8.0.28"
}
]
}{
"versions": [
{
"introduced": "0"
},
{
"fixed": "12.22.9"
},
{
"introduced": "14.0.0"
},
{
"fixed": "14.18.3"
},
{
"introduced": "16.0.0"
},
{
"fixed": "16.13.2"
},
{
"introduced": "17.0.0"
},
{
"fixed": "17.3.1"
},
{
"introduced": "0"
},
{
"last_affected": "11.0"
}
]
}