dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-41230

HIGH · 7.5 CVSS v3.1 Published 2025-05-20
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
VMware Cloud Foundation contains an information disclosure vulnerability. A malicious actor with network access to port 443 on VMware Cloud Foundation may exploit this issue to gain access to sensitive information.

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

VMware Cloud Foundation contains an information disclosure vulnerability accessible via network requests to port 443 (HTTPS). A remote attacker without authentication may exploit this issue to view sensitive data that should not be exposed.

MitigationApply the VMware security patch for CVE-2025-41230 to remediate the vulnerability. Restrict network access to port 443 to trusted sources until the patch can be applied.

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

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
High
Integrity
None
Availability
None

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

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 VMware Cloud Foundation is deployed
    Check your inventory or run: grep -i 'vmware.*cloud.*foundation' /etc/*release* 2>/dev/null or check vCenter/SDDC Manager console for product version
    Affected if Product is VMware Cloud Foundation and port 443 is network-accessible
  2. Identify the installed version
    Log into SDDC Manager or vCenter and navigate to the product information page to view the exact version number. Compare against any VMware security advisories for CVE-2025-41230
    Affected if Version is unpatched per VMware's security advisory for this CVE
  3. Verify port 443 is exposed to the network
    Run 'nmap -p 443 <your-vcf-host>' or use 'curl -k -I https://<your-vcf-host>/' from an untrusted network perspective to confirm HTTPS is reachable externally
    Affected if Port 443 responds to requests from untrusted networks without authentication
  4. Check for unauthenticated sensitive data exposure
    Send a crafted HTTPS request to the VCF management interface without credentials and inspect the response for sensitive configuration files, credentials, or internal data that should require authentication
    Affected if Unauthenticated requests to port 443 return sensitive information that should be protected

You are affected if VMware Cloud Foundation is running with port 443 exposed to untrusted networks and the installation lacks the CVE-2025-41230 patch.

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

Apply the VMware security patch for CVE-2025-41230 to remediate the vulnerability. Restrict network access to port 443 to trusted sources until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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