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.
This vulnerability carries a HIGH severity rating with a CVSS v3.1 score of 7.5, indicating it can be exploited remotely over the network with relatively low complexity without requiring user interaction and does not require pre-existing privileges . The vulnerability impacts and availability (service disruption) for affected systems. Impacting 2 products from openssl, from nodejs organizations running these solutions should prioritize assessment and patching.
First disclosed in 2017, this vulnerability was reported during a period defined by widespread IoT adoption challenges, mobile security concerns, and the emergence of advanced persistent threat (APT) techniques. Contemporary mitigation strategies focused on secure development practices and third-party component vetting.
2017-05-04T19:29:00.353
2026-06-17T01:18:48.320
Modified
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 |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For openssl's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.