.NET Core July Update Relased

In this month' update, Microsoft focused on security issues solving
11 July 2018   836

Microsoft has posted an open version of the .NET Core update. It covers .NET Core 1.0.12, .NET Core 1.1.9, .NET Core 2.0.9, and .NET Core 2.1.2.

Key changes in .NET Core

Microsoft focused on solving security problems. Fixed some vulnerabilities in ASP.NET Core. Fixed a bug when interrupting an incorrect request, allowing an attacker to implement a denial-of-service attack. In addition, the company has compiled a guide for developers, in whose products this vulnerability is present.

Fixed an error that allowed to produce an infinite number of authorization attempts. Vulnerability made the product unstable to brute force. Now the application will count the number of authentication attempts.

In ASP.NET Core, a bug in the processing of certificates has been fixed, which made it possible to present data with an expired term on demand.

Download is available at Microsoft website.

NET Core 2.1 came out in late May 2018, and Microsoft regularly updates this platform.

Ledger to Discover HSM Vulnerability

HSM is an external device designed to store public and private keys used to generate digital signatures and to encrypt data, used by banks, exchanges, etc
10 June 2019   1253

A group of researchers from Ledger identified several vulnerabilities in the Hardware Security Module (HSM) devices, which can be used to extract keys or perform a remote attack to replace the firmware of an HSM device. The problem report is currently available only in French, the English-language report is scheduled to be published in August during the Blackhat USA 2019 conference. HSM is a specialized external device designed to store public and private keys used to generate digital signatures and to encrypt data.

HSM allows you to significantly increase protection, as it completely isolates keys from the system and applications, only by providing an API to perform basic cryptographic primitives implemented on the device side. Typically, HSM is used in areas where you need to provide the highest protection, for example, in banks, cryptocurrency exchanges, certification centers for checking and generating certificates and digital signatures.

The proposed attack methods allow an unauthenticated user to gain complete control over the contents of the HSM, including extracting all the cryptographic keys and administrative credentials stored on the device. The problems are caused by a buffer overflow in the internal PKCS # 11 command handler and an error in the implementation of the cryptographic protection of the firmware, which bypasses the firmware check using the PKCS # 1v1.5 digital signature and initiates loading the own firmware in the HSM.

The name of the manufacturer, the HSM devices of which have vulnerabilities, has not yet been disclosed, but it is argued that the problem devices are used by some large banks and cloud service providers. At the same time it is reported that information about the problems was previously sent to the manufacturer and it has already eliminated vulnerabilities in the fresh firmware update. Independent researchers suggest that the problem may be in the devices of the company Gemalto, which in May released an update to Sentinel LDK with the elimination of vulnerabilities, access to information about which is still closed.