Microsoft.Identity.Web
Affected
- introduced
3.2.0, fixed3.8.2(ecosystem)
Fixed versions
3.8.2
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2025-32016
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
Impact
_What 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
Patches
_Has 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.
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
You can work around the issue in the following ways:
LogLevel = Information for the Microsoft.Identity.Web namespace Recommendation for production environment
Avoid using ClientCredentials with `CredentialDescriptions` which CredentialSource is ClientSecret, or Base64Encoded, or Path. Rather use certificate from KeyVault or a certificate store, or Federation identity credential with Managed identity.
References
_Are there any links users can visit to find out more?_
Medium Basis: The source's own band: MODERATE
3.2.0, fixed 3.8.2 (ecosystem)3.8.2
The export has no generic command for this ecosystem.
7.1.0, fixed 9.0.0 (ecosystem)9.0.0
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0