Skip to content
Fencer Intel
low 3.9

CVE-2024-27086 json

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

published 2y ago modified 2mo ago also GHSA-x674-v45j-fwxw , EUVD-2024-1332

cvss
3.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 8%
public exploits
0
none known

Summary

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.

Patch / fix

  • nuget Microsoft.Identity.Client 4.59.1, 4.60.3

Is CVE-2024-27086 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2y ago

Exploit prediction

0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.9 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
GitHub 3.1 3.9 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
nuget Microsoft.Identity.Client
>=4.48.0, <4.59.1
>=4.60.0, <4.60.3
4.59.1
4.60.3

Affected products

  • AzureAD microsoft-authentication-library-for-dotnet

Classification

Weakness
  • CWE-926 Improper Export of Android Application Components
  • CWE-863 Incorrect Authorization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.