LowGHSA-x674-v45j-fwxwCVE-2024-27086

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

Published 16 Apr 2024 · Updated 10 Sept 2026

Is your project on an affected Microsoft.Identity.Client?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=4.48.0 <4.59.1
Fixed in
4.59.1
Update to the fixed version for your release line, for example:dotnet add package Microsoft.Identity.Client --version 4.59.1
Affected
>=4.60.0 <4.60.3
Fixed in
4.60.3
Update to the fixed version for your release line, for example:dotnet add package Microsoft.Identity.Client --version 4.60.3

Details

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

Impact

MSAL.NET 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:

<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 for latest guidance and best practices on configuring client applications using the library.

Is GHSA-x674-v45j-fwxw in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected Microsoft.Identity.Client, and gives you the command that fixes it.

More advisories for Microsoft.Identity.Client

  • MediumCVE-2024-35255Azure Identity Libraries and Microsoft Authentication Library Elevation of Privilege Vulnerability · 11 Jun 2024
Microsoft.Identity.Client security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.