🛡️ CVE-2024-27086 — microsoft.identity.client

🟢 CVSS 3.9 — Low ✅ No Known Exploit CWE-863 NVD
3.9
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

MSAL.NET applications targeting Xamarin Android and .NET Android (MAUI) susceptible to local denial of service

>[!IMPORTANT]

>ONLY applications targeting Xamarin Android and .NET Android (MAUI) are impacted. All others can safely dismiss this CVE.

Impact

[MSAL.NET](https://www.nuget.org/packages/Microsoft.Identity.Client/) applications targeting Xamarin Android and .NET Android (e.g., MAUI) using the library from versions 4.48.0 to 4.60.3 (inclusive, except 4.59.1 and 4.60.3) are impacted by a low severity vulnerability.

A malicious application running on a customer Android device can (1) inject HTML/JavaScript in an embedded web view exported by affected applications, or (2) 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.

Patches

MSAL.NET version 4.60.3 includes the fix. We recommend all users of MSAL.NET that are building public client applications for Android update to the latest version.

Workarounds

We recommend developers update to the latest version of MSAL.NET. If that is not possible, a developer may explicitly mark the MSAL.NET activity non-exported:

```xml

<activity android:name="microsoft.identity.client.AuthenticationAgentActivity" android:configChanges="orientation|screenSize" android:exported="false">

<intent-filter>

<action android:name="android.intent.action.VIEW" />

<category android:name="android.intent.category.DEFAULT" />

<category android:name="android.intent.category.BROWSABLE" />

<data android:scheme="msalYOUR_CLIENT_ID" android:host="auth" />

</intent-filter>

</activity>

```

References

Refer to [MSAL.NET documentation](https://learn.microsoft.com/entra/msal/dotnet/) for latest guidance and best practices on configuring client applications using the library.

How this vulnerability can be exploited

This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity low, availability low.

Weakness class

CVE-2024-27086 is classified as CWE-863: Incorrect Authorization. An authorisation check runs but reaches the wrong conclusion, permitting actions it should refuse.

Affected software

CVE-2024-27086 is recorded against 2 packages.

  • microsoft.identity.client (from 4.60.0 up to 4.60.3)
  • unknown

Timeline and source

Published on 16 April 2024 and last revised on 23 April 2024. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Package)
learn.microsoft.com (Web)
www.nuget.org (Web)

Details

Severity LOW
CVSS Score 3.9
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
CWE CWE-863
Public Exploit ✅ No
Source NVD
Published 2024-04-16
Updated 2026-08-12
Modified 2024-04-23
Fix URL N/A

Affected Packages

Software From version Fixed in
microsoft.identity.client 4.60.0 4.60.3
unknown — —

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2024-27086?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2024-27086 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.