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.
2017-05-04T19:29:00.353
2025-04-20T01:37:25.860
Deferred
CVSSv3.1: 7.5 (HIGH)
AV:N/AC:L/Au:N/C:N/I:N/A:P
10.0
2.9
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | openssl | openssl | 1.1.0a | Yes |
Application | openssl | openssl | 1.1.0b | Yes |
Application | openssl | openssl | 1.1.0c | Yes |
Application | openssl | openssl | 1.0.2 | Yes |
Application | openssl | openssl | 1.0.2 | Yes |
Application | openssl | openssl | 1.0.2 | Yes |
Application | openssl | openssl | 1.0.2 | Yes |
Application | openssl | openssl | 1.0.2a | Yes |
Application | openssl | openssl | 1.0.2b | Yes |
Application | openssl | openssl | 1.0.2c | Yes |
Application | openssl | openssl | 1.0.2d | Yes |
Application | openssl | openssl | 1.0.2e | Yes |
Application | openssl | openssl | 1.0.2f | Yes |
Application | openssl | openssl | 1.0.2h | Yes |
Application | openssl | openssl | 1.0.2i | Yes |
Application | openssl | openssl | 1.0.2j | Yes |
Application | nodejs | node.js | ≤ 4.1.2 | Yes |
Application | nodejs | node.js | < 4.7.3 | Yes |
Application | nodejs | node.js | ≤ 5.12.0 | Yes |
Application | nodejs | node.js | ≤ 6.8.1 | Yes |
Application | nodejs | node.js | < 6.9.5 | Yes |
Application | nodejs | node.js | < 7.5.0 | Yes |