LiveActive security incident?Get immediate response
CVE Record

CVE-2017-3731: Truncated packet could crash via OOB read

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This OpenSSL flaw can crash a TLS client or server on 32-bit systems when a truncated packet is processed with certain ciphers. The documented impact is availability disruption, not data theft. Exposure is mainly legacy or embedded 32-bit deployments using affected OpenSSL versions and cipher configurations. Most exposure is in older 32-bit Linux, BSD, appliance, mobile, or embedded environments that bundled vulnerable OpenSSL. Modern 64-bit systems and configurations without the named ciphers are less likely to be exposed, but vendor packages and statically linked applications still need inventory review. Prioritize remediation for internet-facing TLS services, security appliances, and legacy 32-bit platforms. The likely business impact is service disruption rather than compromise, but OpenSSL’s broad reuse means hidden exposure in vendor products is plausible. Mitigation focus: Upgrade OpenSSL 1.1.0 deployments to 1.1.0d or later.; Upgrade OpenSSL 1.0.2 deployments to 1.0.2k or later.; Disable RC4-MD5 where OpenSSL 1.0.2 cannot be immediately updated..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-3731 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
14Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
OpenSSLOpenSSLopenssl-1.1.0, openssl-1.1.0a, openssl-1.1.0b, openssl-1.1.0c, openssl-1.0.2, openssl-1.0.2a, openssl-1.0.2b, openssl-1.0.2c, openssl-1.0.2d, openssl-1.0.2e, openssl-1.0.2f, openssl-1.0.2g, openssl-1.0.2h, openssl-1.0.2i, openssl-1.0.2jListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.