This post was originally published on this site.
🚨 Security Advisory: CVE-2017-3736 There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.
A new vulnerability has been identified and published under CVE-2017-3736 as part of Microsoft’s Security Update Guide on Tue, 02 Jun 2026 01:46:51 -0700.
Organizations should review this advisory to understand potential risks, affected systems, and recommended mitigation steps. Timely awareness of vulnerabilities is critical for maintaining a strong cybersecurity posture and reducing exposure to emerging threats.
🔎 What this means for you:
This vulnerability may impact systems, applications, or services commonly used in enterprise environments. Security teams should evaluate exposure and apply updates or mitigations as soon as possible.
CVE-2017-3736 There is a carry propagating bug in the x86_64 Montgomery squaring procedure in OpenSSL before 1.0.2m and 1.1.0 before 1.1.0g. No EC algorithms are affected. Analysis suggests that attacks against RSA and DSA as a result of this defect would be very difficult to perform and are not believed likely. Attacks against DH are considered just feasible (although very difficult) because most of the work necessary to deduce information about a private key may be performed offline. The amount of resources required for such an attack would be very significant and likely only accessible to a limited number of attackers. An attacker would additionally need online access to an unpatched system using the target private key in a scenario with persistent DH parameters and a private key that is shared between multiple clients. This only affects processors that support the BMI1, BMI2 and ADX extensions like Intel Broadwell (5th generation) and later or AMD Ryzen.
🛡️ Recommended Actions
- Review the full advisory from Microsoft: View advisory
- Identify affected systems within your environment
- Apply patches or mitigations where applicable
- Monitor for suspicious activity related to this vulnerability
📡 Stay Ahead of Threats
This post is part of DataComm's vulnerability intelligence feed designed to keep your organization informed of the latest security risks.
For deeper insights, threat detection, and response capabilities, consider implementing a banking-grade security strategy that includes continuous monitoring, threat intelligence, and rapid incident response.
Our Status
DataComm is reviewing affected systems and validating compliance in accordance with vendor guidance. Customers requiring assistance are encouraged to contact our support team.
Support: support@datacomm.com
Phone: (877) 544-3655
Source: Microsoft Security Response Center (MSRC)
