Reads a public metadata endpoint on flagged hosts. Advisory
Detect
Fingerprints vCenter and flags CVE-2022-22948 by version.
Report
Counts checked, product, affected, and confirmed.
Targets
Hosts, IPs, or URLs, one per line. Empty input uses localhost.
Overview
This workflow finds VMware vCenter Server and sorts each host by whether its version falls in the CVE-2022-22948 range. vCenter is the control plane for the hypervisor estate. CVE-2022-22948 is information disclosure that CISA listed on KEV after public use. A leftover 7.0 appliance still serves the same vSphere login you already know. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on vSphere), reads the version from / with a fallback to the root body, and compares that number to the range table in the graph. Every host comes back affected or not, so a fleet advisory becomes an evidenced list for exposure management. CVE-2022-22948 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that GETs a public metadata endpoint. It does not dump secrets or write files.
Run it on a schedule when the estate changes. New hosts and delayed patch windows are the reason the same check is worth more the second week than the first.
Pipeline
Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
Fingerprint each host as VMware vCenter Server from the public page title, then GET / and parse the version. A host counts as affected only when the fingerprint matches and the version is inside the encoded range.
Confirm only those flagged hosts by GETting a public metadata endpoint.
Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
Emit the summary counts: hosts checked, product hits, affected, confirmed, and errors.
Inputs
Target list. Hostnames, IP addresses, CIDR ranges, or URLs, one per line. JSONL with a url field also works. Point it at scope you are authorised to test. Fingerprint is read-only GET. Confirm is a GET of a public metadata endpoint, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether VMware vCenter Server was detected, the version read, the affected flag, and whether the public-metadata confirm succeeded.
summary.json. Counts across the list: targets, product hits, affected, and errors.
Integrations
HTTP. Unauthenticated GET to the product root and (on flagged hosts only) a public metadata endpoint.
Sample output
The records below are illustrative and do not come from a real run. They show one VMware vCenter Server host inside the CVE-2022-22948 range, one patched host, and one host that is not the product.
Which VMware vCenter Server versions does this flag?
exactly 6.5, 6.7, and 7.0 in the check table. any build the check does not match as 6.5, 6.7, or 7.0 is the floor the graph treats as not affected. The compare uses the version the product itself served.
Does a flagged host mean CVE-2022-22948 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only GETs a public metadata endpoint. Treat a confirmed row as evidence that endpoint still answers, not as proof someone already used it.
Is this check safe on production?
Yes. Fingerprint is read-only GET. Confirm is another GET of a public metadata endpoint, only on hosts already in range. It does not log in, dump secrets, or write files.
Does the check need credentials?
No. It fingerprints the public page and reads / the way an external scanner would.
What is CVE-2022-22948?
Information disclosure in VMware vCenter Server. CISA listed it on KEV after public use. The check flags exactly 6.5, 6.7, and 7.0. This workflow flags by version, then confirms with a public-metadata GET. It does not dump secrets.