Описание
When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20.
A vulnerability has been identified in the Node.js, where an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario.
Затронутые пакеты
Платформа | Пакет | Состояние | Рекомендация | Релиз |
---|---|---|---|---|
Red Hat Enterprise Linux 8 | nodejs:14/nodejs | Will not fix | ||
Red Hat Software Collections | rh-nodejs14-nodejs | Not affected | ||
Red Hat Enterprise Linux 8 | nodejs | Fixed | RHSA-2023:4536 | 08.08.2023 |
Red Hat Enterprise Linux 8 | nodejs | Fixed | RHSA-2023:4537 | 08.08.2023 |
Red Hat Enterprise Linux 8.6 Extended Update Support | nodejs | Fixed | RHSA-2023:5361 | 26.09.2023 |
Red Hat Enterprise Linux 9 | nodejs | Fixed | RHSA-2023:4330 | 31.07.2023 |
Red Hat Enterprise Linux 9 | nodejs | Fixed | RHSA-2023:4331 | 31.07.2023 |
Red Hat Enterprise Linux 9.0 Extended Update Support | nodejs | Fixed | RHSA-2023:5533 | 09.10.2023 |
Показывать по
Дополнительная информация
Статус:
5.3 Medium
CVSS3
Связанные уязвимости
When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20.
When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20.
When an invalid public key is used to create an x509 certificate using ...
When an invalid public key is used to create an x509 certificate using the crypto.X509Certificate() API a non-expect termination occurs making it susceptible to DoS attacks when the attacker could force interruptions of application processing, as the process terminates when accessing public key info of provided certificates from user code. The current context of the users will be gone, and that will cause a DoS scenario. This vulnerability affects all active Node.js versions v16, v18, and, v20.
Уязвимость функции crypto.X509Certificate() программной платформы Node.js, позволяющая нарушителю вызвать отказ в обслуживании
5.3 Medium
CVSS3