Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

microsoft.identitymodel.protocols.signedhttprequest

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.1NuGetPublished

    Microsoft.IdentityModel.Protocols.SignedHttpRequest remote code execution vulnerability

    CVE-2024-21643 · GHSA-rv9j-c866-gp5h

    Affected
    • NuGet microsoft.identitymodel.protocols.signedhttprequest < 6.34.0; >= 7.0.0-preview, < 7.1.2
    Fixed in
    6.34.07.1.2· Vendor fix available
    Issue
    Impact What kind of vulnerability is it? Who is impacted? Anyone leveraging the SignedHttpRequestprotocol or the SignedHttpRequestValidatoris vulnerable. Microsoft.IdentityModel trusts the jkuclaim by default for the SignedHttpRequestprotocol. This raises the possibility to make any remote or local HTTP GET request. Patches Has the problem been patched? What versions should users upgrade to? The vulnerability has been fixed in Microsoft.IdentityModel.Protocols.SignedHttpRequest. Users should update all their Microsoft.IdentityModel versions to 7.1.2 (for 7x) or higher, 6.34.0 (for 6x) or higher, if using Microsoft.IdentityModel.Protocols.SignedHttpRequest. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? No, users must upgrade. References Are there any links users can visit to find out more? https://aka.ms/IdentityModel/Jan2024/jku

    Recommended action: Upgrade to 7.1.2 or 6.34.0 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →