GHSA-RPQ8-Q44M-2RPG

Vulnerability from github – Published: 2025-04-09 18:58 – Updated: 2025-04-09 18:58
VLAI?
Summary
Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs
Details

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:

  • Logging Level: Logs are generated at the information level.
  • Credential Descriptions: containing:
    • Local file paths with passwords.
    • Base64 encoded values.
    • Client secret.

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:

  • Ensure that service logs are handled securely and access to logs is restricted

  • Don’t use 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?

Severity ?
4.7 (Medium)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "NuGet",
        "name": "Microsoft.Identity.Web"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.2.0"
            },
            {
              "fixed": "3.8.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "NuGet",
        "name": "Microsoft.Identity.Abstractions"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "7.1.0"
            },
            {
              "fixed": "9.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2025-32016"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-532"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2025-04-09T18:58:35Z",
    "nvd_published_at": "2025-04-09T16:15:24Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\n**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.\n\n**Impact:** The vulnerability impacts service logs that meet the following criteria:\n\n- **Logging Level:** Logs are generated at the information level.\n- **Credential Descriptions:** containing:\n    - Local file paths with passwords.\n    - Base64 encoded values.\n    - Client secret.\n    \nAdditionally, 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.\n\nIf your service logs are handled securely, you are not impacted. \n\nOtherwise, the following table shows when you can be impacted \n\u00a0 | Log Level Information for Microsoft.Identity.Web | Invalid Certificate\n-- | -- | --\nOne of the ClientCredentials credential description has a CredentialSource = Base64Encoded or (CredentialSource = Path) | Impacted | Impacted\nOne of the ClientCredentials credential description is a Client secret (CredentialSource = ClientSecret) | Impacted | Not impacted\nOther credential descriptions | Not Impacted | Not Impacted\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\nTo mitigate this vulnerability, update to Microsoft.Identity.Web 3.8.2 or Microsoft.Identity.Abstractions 9.0.0.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\nYou can work around the issue in the following ways: \n\n- Ensure that service logs are handled securely and access to logs is restricted\n\n- Don\u2019t use `LogLevel = Information` for the Microsoft.Identity.Web namespace \n\n### Recommendation for production environment\nAvoid using `ClientCredentials` with [`CredentialDescriptions`](https://learn.microsoft.com/en-us/dotnet/api/microsoft.identity.abstractions.credentialdescription.base64encodedvalue?view=msal-model-dotnet-latest) which `CredentialSource` is `ClientSecret`, or `Base64Encoded`, or `Path`. Rather use certificate from KeyVault or a certificate store, or Federation identity credential with Managed identity.\n\n### References\n_Are there any links users can visit to find out more?_",
  "id": "GHSA-rpq8-q44m-2rpg",
  "modified": "2025-04-09T18:58:35Z",
  "published": "2025-04-09T18:58:35Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/AzureAD/microsoft-identity-web/security/advisories/GHSA-rpq8-q44m-2rpg"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32016"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/AzureAD/microsoft-identity-web"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Microsoft Identity Web Exposes Client Secrets and Certificate Information in Service Logs"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.