Описание
If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needs-triage |
| devel | not-affected | 18.7.0+dfsg-5ubuntu1 |
| esm-apps/bionic | needed | |
| esm-apps/focal | needed | |
| esm-apps/jammy | not-affected | 12.22.9~dfsg-1ubuntu3.6 |
| esm-apps/noble | not-affected | 18.7.0+dfsg-5ubuntu1 |
| esm-apps/xenial | needed | |
| esm-infra-legacy/trusty | not-affected | code not present |
| focal | ignored | end of standard support, was needed |
| hirsute | ignored | end of life |
Показывать по
5 Medium
CVSS2
5.3 Medium
CVSS3
Связанные уязвимости
If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.
If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.
If the Node.js https API was used incorrectly and "undefined" was in p ...
If the Node.js https API was used incorrectly and "undefined" was in passed for the "rejectUnauthorized" parameter, no error was returned and connections to servers with an expired certificate would have been accepted.
Уязвимость компонента API https программной платформы Node.js, позволяющая нарушителю оказать воздействие на целостность данных
5 Medium
CVSS2
5.3 Medium
CVSS3