Truncated packet could crash via OOB read
Published May 4, 2017 · Updated Oct 23, 2026
Original summary
Normalized public record · Updated Oct 23, 2026
Truncated packet could crash via OOB read
Publisher and source text is retained separately from QFinch interpretation.
QFinch assessment
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.
Evidence: public source recordsAffected products
| Affected package, product or range | Fix status |
|---|---|
| Consult the referenced vendor advisory for affected versions. | Consult source advisory |
Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.
Remediation
Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.
- Confirm the affected product and reachable code path exist in your environment.
- Apply the vendor-supported patch or mitigation from the primary advisory.
- Rescan the exact deployed revision and retain verification evidence.
Evidence coverage
- SSVC priority
- MEDIUM
- Confidence
- 15%
- Aliases
- None reported
Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.
Sources and record history
- RHSA-2018:2185 ↗
- RHSA-2018:2186 ↗
- security.netapp.com ↗
- www.oracle.com ↗
- 95813 ↗
- RHSA-2017:0286 ↗
- FreeBSD-SA-17:02 ↗
- www.openssl.org ↗
- 1037717 ↗
- www.oracle.com ↗
- www.tenable.com ↗
- source.android.com ↗
Record history
Published May 4, 2017 · Last refreshed Oct 23, 2026