Total vulnerabilities in the database
If an SSL/TLS server or client is running on a 32-bit host, and a specific cipher is being used, then a truncated packet can cause that server or client to perform an out-of-bounds read, usually resulting in a crash. For OpenSSL 1.1.0, the crash can be triggered when using CHACHA20/POLY1305; users should upgrade to 1.1.0d. For Openssl 1.0.2, the crash can be triggered when using RC4-MD5; users who have not disabled that algorithm should update to 1.0.2k.
| Software | From | Fixed in |
|---|---|---|
| openssl / openssl | 1.1.0c | 1.1.0c.x |
| openssl / openssl | 1.1.0b | 1.1.0b.x |
| openssl / openssl | 1.1.0a | 1.1.0a.x |
| openssl / openssl | 1.0.2a | 1.0.2a.x |
| openssl / openssl | 1.0.2e | 1.0.2e.x |
| openssl / openssl | 1.0.2j | 1.0.2j.x |
| openssl / openssl | 1.0.2b | 1.0.2b.x |
| openssl / openssl | 1.0.2h | 1.0.2h.x |
| openssl / openssl | 1.0.2c | 1.0.2c.x |
| openssl / openssl | 1.0.2-beta3 | 1.0.2-beta3.x |
| openssl / openssl | 1.0.2-beta1 | 1.0.2-beta1.x |
| openssl / openssl | 1.0.2 | 1.0.2.x |
| openssl / openssl | 1.0.2f | 1.0.2f.x |
| openssl / openssl | 1.0.2-beta2 | 1.0.2-beta2.x |
| openssl / openssl | 1.0.2i | 1.0.2i.x |
| openssl / openssl | 1.0.2d | 1.0.2d.x |
| nodejs / node.js | 4.0.0 | 4.1.2.x |
| nodejs / node.js | 6.0.0 | 6.8.1.x |
| nodejs / node.js | 5.0.0 | 5.12.0.x |
| nodejs / node.js | 7.0.0 | 7.5.0 |
| nodejs / node.js | 6.9.0 | 6.9.5 |
| nodejs / node.js | 4.2.0 | 4.7.3 |