dbcve.org
Azure Health BotApplication · Microsoft

CVE-2025-21384

HIGH · 8.8 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An authenticated attacker can exploit an Server-Side Request Forgery (SSRF) vulnerability in Microsoft Azure Health Bot to elevate privileges over a network.

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 · high confidence

CVE-2025-21384 is an authenticated Server-Side Request Forgery (SSRF) vulnerability in Microsoft Azure Health Bot. An attacker who has valid authentication credentials can exploit this flaw to make the service perform requests to arbitrary internal or external resources, potentially bypassing network boundaries and elevating privileges within the Azure environment.

MitigationMicrosoft has released patches for this vulnerability; organizations using Azure Health Bot should apply the latest security updates immediately. Additionally, network segmentation and strict firewall rules should be implemented to limit outbound requests from the Health Bot service.

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
Azure Health BotApplication
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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Confirm Azure Health Bot deployment
    In Azure Portal, search for 'Health Bot' in All Resources, or use Azure CLI command: az resource list --query "[?type=='Microsoft.HealthcareApis/bots']"
    Affected if No Azure Health Bot resource exists in the subscription - not affected
  2. Identify outbound network traffic from Health Bot
    Use Azure Network Watcher or NSG flow logs to review outbound connections originating from the Health Bot's subnet or associated IP addresses. Look for requests to unexpected internal (e.g., 10.x.x.x, 192.168.x.x) or external destinations.
    Affected if Unusual outbound requests to internal infrastructure or unexpected external URLs are observed in network logs
  3. Review Azure Activity Log for Health Bot operations
    In Azure Portal, navigate to the Health Bot resource, then Monitoring > Activity Log. Filter by the Health Bot resource and look for API operations, especially outbound HTTP requests or webhook executions.
    Affected if Log entries show requests to internal endpoints, Azure management APIs, or other unexpected URLs that were not initiated by legitimate workflows
  4. Examine Azure Health Bot connector and webhook configurations
    In Azure Portal, go to the Health Bot resource > Tools > Connectors or Configuration. Review any configured webhooks, data connections, or integration endpoints that could be leveraged for SSRF.
    Affected if Connectors are configured to arbitrary URLs, especially internal infrastructure URLs, without proper validation
  5. Check for unauthorized data exfiltration patterns
    Review Health Bot conversation logs and data flow records for patterns indicating the bot has accessed internal Azure services (e.g., Azure Storage, Key Vault, SQL databases) via crafted requests.
    Affected if Evidence exists of the Health Bot accessing resources outside its intended scope, particularly internal Azure services

If Azure Health Bot is deployed in the subscription and unusual outbound requests or unauthorized resource access is observed in logs or network traffic, the environment is likely affected by this SSRF vulnerability.

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

Microsoft has released patches for this vulnerability; organizations using Azure Health Bot should apply the latest security updates immediately. Additionally, network segmentation and strict firewall rules should be implemented to limit outbound requests from the Health Bot service.

Fix this in Azure Health Bot Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-21384 — 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-2025-21384 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