AzureAD microsoft-authentication-library-for-dotnet up to 4.59.0/4.60.2 improper export of android application components

Summaryinfo

A vulnerability was found in AzureAD microsoft-authentication-library-for-dotnet up to 4.59.0/4.60.2. It has been classified as problematic. This affects an unknown part. Performing a manipulation results in improper export of android application components. This vulnerability is identified as CVE-2024-27086. The attack is only possible with local access. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as problematic, was found in AzureAD microsoft-authentication-library-for-dotnet up to 4.59.0/4.60.2. This affects an unknown code block. The manipulation with an unknown input leads to a improper export of android application components vulnerability. CWE is classifying the issue as CWE-926. The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains. This is going to have an impact on integrity, and availability. The summary by CVE is:

The MSAL library enabled acquisition of security tokens to call protected APIs. MSAL.NET applications targeting Xamarin Android and .NET Android (e.g., MAUI) using the library from versions 4.48.0 to 4.60.0 are impacted by a low severity vulnerability. A malicious application running on a customer Android device can cause local denial of service against applications that were built using MSAL.NET for authentication on the same device (i.e., prevent the user of the legitimate application from logging in) due to incorrect activity export configuration. MSAL.NET version 4.60.1 includes the fix. As a workaround, a developer may explicitly mark the MSAL.NET activity non-exported.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-27086 since 02/19/2024. The exploitability is told to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

Upgrading to version 4.59.1 or 4.60.3 eliminates this vulnerability. Applying the patch 413e319472ccf48c86647f19fa2aa49ff6038488 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Software Library

Vendor

• AzureAD

Name

• microsoft-authentication-library-for-dotnet

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9
• 4.10
• 4.11
• 4.12
• 4.13
• 4.14
• 4.15
• 4.16
• 4.17
• 4.18
• 4.19
• 4.20
• 4.21
• 4.22
• 4.23
• 4.24
• 4.25
• 4.26
• 4.27
• 4.28
• 4.29
• 4.30
• 4.31
• 4.32
• 4.33
• 4.34
• 4.35
• 4.36
• 4.37
• 4.38
• 4.39
• 4.40
• 4.41
• 4.42
• 4.43
• 4.44
• 4.45
• 4.46
• 4.47
• 4.48
• 4.49
• 4.50
• 4.51
• 4.52
• 4.53
• 4.54
• 4.55
• 4.56
• 4.57
• 4.58
• 4.59.0
• 4.60.0
• 4.60.1
• 4.60.2

License

• open-source

Website

• Product: https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion