Microsoft Security Transport Layer Protocol certificates and private keys are exposed for more than 100 days. attackers who obtain the certificates can initiate attacks at will, and 100 days attackers
Recently, software developers accidentally discovered that Microsoft's Dynamics 365 TLS Certificate and private key had been exposed for more than 100 days, hackers who obtain the certificate can access any sandbox environment and launch man-in-the-middle attacks on it.
Why is the exposed Security Transport Layer Protocol certificate and private key causing such serious consequences? This is because exposing the private key of the TLS Certificate means that attackers can decrypt the traffic protected by the digital certificate and impersonate the server with the private key of the TLS Certificate, in this way, the communication of the victim user can be disclosed without being detected by the security mechanism.
Dynamics 365 TLS is a new cloud business application solution launched by Microsoft. It can effectively help enterprises adapt to market changes and continue to develop, if attackers extract leaked certificates, it means that all enterprises that use the Dynamics 365 sandbox environment will face tough security issues. In fact, hackers only need to use a C ++ applet to export the private key of the TLS Certificate. Because the certificate is used to decrypt the Web traffic between the user and the server, therefore, attackers can extract certificates to access any sandbox environment.
Previously, developers who found the problem reported the vulnerability issue to Microsoft as early as middle August. However, even if the reporter described the vulnerability in detail and provided evidence such as the private key and encrypted copy, microsoft still believes that this issue is not a vulnerability because attackers need to obtain administrator creden。 to extract the vulnerability. After the event, although developers still reflected the problem for many times, the problem could not be solved until German security researchers tried to submit a vulnerability report through the Mozilla vulnerability tracker, and Microsoft fixed the vulnerability again in early December.