Node.js versions which bundle an unpatched version of OpenSSL or run against a dynamically linked version of OpenSSL which are unpatched are vulnerable to the Marvin Attack - https://people.redhat.com/~hkario/marvin/, if PCKS #1 v1.5 padding is allowed when performing RSA descryption using a private key.
Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system behavior and infer protected information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | RedHat | nodejs:18-8090020240301110609.a75119d5 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:20-8090020240228165436.a75119d5 | * |
| Red Hat Enterprise Linux 8.8 Extended Update Support | RedHat | nodejs:18-8080020240322102042.63b34585 | * |
| Red Hat Enterprise Linux 9 | RedHat | nodejs:18-9030020240301111035.rhel9 | * |
| Red Hat Enterprise Linux 9 | RedHat | nodejs:20-9030020240229115828.rhel9 | * |
| Red Hat Enterprise Linux 9.2 Extended Update Support | RedHat | nodejs:18-9020020240322155241.rhel9 | * |
| Nodejs | Ubuntu | bionic | * |
| Nodejs | Ubuntu | mantic | * |
| Nodejs | Ubuntu | trusty | * |
| Nodejs | Ubuntu | trusty/esm | * |
| Nodejs | Ubuntu | upstream | * |
| Nodejs | Ubuntu | xenial | * |
In some instances, knowing when data is transmitted between parties can provide a malicious user with privileged information. Also, externally monitoring the timing of operations can potentially reveal sensitive data. For example, a cryptographic operation can expose its internal state if the time it takes to perform the operation varies, based on the state. Covert channels are frequently classified as either storage or timing channels. Some examples of covert timing channels are the system’s paging rate, the time a certain transaction requires to execute, and the time it takes to gain access to a shared bus.