CVE-2017-3731HighMicrosoft CVSS 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Microsoft advisory for CVE-2017-3731

Published
April 26, 2026
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2017-3731 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-3731. This page also shows what EchelonGraph holds for CVE-2017-3731, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products6

  • azl3 shim-unsigned-aarch64 16.1-1 on Azure Linux 3.0
  • azl3 shim-unsigned-aarch64 16.1-2 on Azure Linux 3.0
  • azl3 shim-unsigned-x64 16.1-1 on Azure Linux 3.0
  • azl3 shim-unsigned-x64 16.1-2 on Azure Linux 3.0
  • cbl2 shim-unsigned-aarch64 15-5 on CBL Mariner 2.0
  • cbl2 shim-unsigned-x64 15.8-1 on CBL Mariner 2.0

🧭 EchelonGraph on CVE-2017-3731

EchelonGraph score
8.2 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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.

Published by OpenSSL Software Foundation, the CVE Numbering Authority that assigned CVE-2017-3731, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (1)