dbcve.org
Entra IdApplication · Microsoft

CVE-2024-43477

HIGH · 7.5 CVSS v3.1 Published 2024-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper access control in Decentralized Identity Services resulted in a vulnerability that allows an unauthenticated attacker to disable Verifiable ID's on another tenant.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is an improper access control vulnerability in Decentralized Identity Services where the system fails to properly validate tenant boundaries. An unauthenticated (unauthenticated) attacker can make requests that should require authentication and proper tenant context, allowing them to disable Verifiable IDs belonging to users in different tenant contexts. This represents a tenant isolation failure in the authorization logic.

MitigationImplement proper authentication enforcement and tenant context validation on all Verifiable ID management endpoints to ensure users can only modify IDs within their own tenant. Add explicit tenant authorization checks before any disable/modify operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Entra IdApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Verifiable Credentials feature is enabled
    In Microsoft Entra admin center, navigate to Identity > Verifiable Credentials and check if the feature is provisioned or active in your tenant.
    Affected if Verifiable Credentials is enabled and actively used in the tenant, exposing the tenant to this authorization bypass vulnerability.
  2. Review Azure AD sign-in logs for disable operations
    Access Microsoft Entra admin center > Monitoring > Sign-in logs and filter for operations targeting Verifiable Credentials, specifically look for 'Disable' action types originating from unauthenticated or cross-tenant IP addresses.
    Affected if Sign-in logs show disable operations on Verifiable IDs that originated from unauthenticated requests or IP addresses not associated with legitimate tenant administrators.
  3. Check Azure AD audit logs for Verifiable Credential modifications
    Navigate to Microsoft Entra admin center > Monitoring > Audit logs and filter the 'Category' for 'Verifiable Credentials' or 'Identity Verification Services' to review recent credential disable events.
    Affected if Audit logs reveal Verifiable ID disable events that were performed without proper tenant context or authentication claims matching the target tenant.
  4. Inspect conditional access policies for Verifiable Credential endpoints
    In Microsoft Entra admin center > Protection > Conditional Access, examine whether policies explicitly require authentication and tenant context for Verifiable Credential management APIs.
    Affected if No conditional access policies are configured to enforce tenant-specific authentication on Verifiable ID management endpoints, indicating the tenant boundary was not enforced.

Your environment is affected if Verifiable Credentials are enabled in your Entra ID tenant and audit logs show unauthorized cross-tenant disable operations or lack of tenant context enforcement on credential management endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication enforcement and tenant context validation on all Verifiable ID management endpoints to ensure users can only modify IDs within their own tenant. Add explicit tenant authorization checks before any disable/modify operations.

Fix this in Entra Id Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43477 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43477 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data