Microsoft.Identity.Abstractions
Contains interfaces and data classes used in the .NET Microsoft authentication libraries (MSAL, IdentityModel, Microsoft.Identity.Web, ...)
View on Github
Activity
- Latest release
- 2w ago
- Total releases
- 51
- Cadence
- ~17 days
- Last 12 months
- 14
Reach
- Stars
- 20
Details
- License
- MIT
- First release
- Oct 18, 2022
| Version | Released | |
|---|---|---|
12.6.1
patch
| ||
12.6.0
minor
| ||
12.5.0
minor
| ||
12.4.0
minor
| ||
12.3.0
minor
| ||
12.2.0
minor
| ||
12.1.0
minor
| ||
12.0.0
major
| ||
11.2.0
minor
| ||
11.1.0
minor
| ||
11.0.0
major
| ||
10.0.0
major
| ||
9.6.0
minor
| ||
9.5.0
minor
| ||
9.4.0
minor
| ||
9.3.0
minor
| ||
9.2.0
minor
| ||
9.1.0
minor
| ||
9.0.0
major
| ||
8.2.0
minor
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
8.1.1
patch
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
8.1.0
minor
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
8.0.0
major
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
7.2.1
patch
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
7.2.0
minor
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
7.1.0
minor
1 CVE
CVE-2025-32016
GHSA-rpq8-q44m-2rpg
Apr 09, 2025
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
4.7
/ 10
Medium
Local
High
Low
None
Unchanged
High
None
None
ImpactWhat kind of vulnerability is it? Who is impacted? Description: This vulnerability affects confidential client applications, including daemons, web apps, and web APIs. Under specific circumstances, sensitive information such as client secrets or certificate details may be exposed in the service logs of these applications. Service logs are intended to be handled securely. Impact: The vulnerability impacts service logs that meet the following criteria:
Additionally, logs of services using Base64 encoded certificates or certificate paths with password credential descriptions are also affected if the certificates are invalid or expired, regardless of the log level. Note that these credentials are not usable due to their invalid or expired status. If your service logs are handled securely, you are not impacted. Otherwise, the following table shows when you can be impacted | Log Level Information for Microsoft.Identity.Web | Invalid Certificate -- | -- | -- One of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted One of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted Other credential descriptions | Not Impacted | Not Impacted PatchesHas the problem been patched? What versions should users upgrade to? To mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0. WorkaroundsIs there a way for users to fix or remediate the vulnerability without upgrading? You can work around the issue in the following ways:
Recommendation for production environmentAvoid using ReferencesAre there any links users can visit to find out more? Affected versions
7.1.0
7.2.0
7.2.1
8.0.0
8.1.0
8.1.1
8.2.0
Fixed in
9.0.0
References Updated Apr 09, 2025 · Source: OSV.dev | ||
7.0.0
major
| ||
6.0.0
major
| ||
5.3.0
minor
| ||
5.2.0
minor
| ||
5.1.0
minor
| ||
5.0.0
major
| ||
4.1.0
minor
| ||
4.0.0
major
| ||
3.2.1
patch
| ||
3.2.0
minor
| ||
3.1.0
minor
| ||
3.0.1
patch
| ||
3.0.0
major
| ||
2.1.0
minor
| ||
2.0.1
patch
| ||
2.0.0
major
| ||
1.2.0
minor
| ||
1.1.0
initial
| ||
1.0.6-preview
pre
| ||
1.0.5-preview
pre
| ||
1.0.4-preview
pre
| ||
1.0.3-preview
pre
| ||
1.0.2-preview
pre
| ||
1.0.1-preview
pre
|