Opens a restricted page through the known traversal. Advisory
Detect
Fingerprints Openfire and flags CVE-2023-32315 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 Ignite Realtime Openfire and sorts each host by whether its version falls in the CVE-2023-32315 range. Openfire is the XMPP admin console people forget after the chat rollout. CVE-2023-32315 is the path traversal that let unauthenticated callers open restricted console pages. CISA put it on KEV because the exploit was public and used. A forgotten 4.7 box still serves login.jsp. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on Openfire), reads the version from /login.jsp 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-2023-32315 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only opens a restricted page through the known traversal. It does not write files or change configuration.
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 Ignite Realtime Openfire from the public page title, then GET /login.jsp 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 opening a restricted page through the known traversal.
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 restricted page through the known traversal, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether Ignite Realtime Openfire was detected, the version read, the affected flag, and whether the restricted-page confirm succeeded.
summary.json. Counts across the list: targets, product hits, affected, and errors.
Integrations
HTTP. Unauthenticated GET to the product root, /login.jsp, and (on flagged hosts only) a restricted page through the known traversal.
Sample output
The records below are illustrative and do not come from a real run. They show one Ignite Realtime Openfire host inside the CVE-2023-32315 range, one patched host, and one host that is not the product.
Which Ignite Realtime Openfire versions does this flag?
3.10.0 through 4.6.7, and 4.7.0 through 4.7.4. 4.6.8 and 4.7.5 and later on those lines is the floor the graph treats as not affected. The compare uses the version the product itself served.
Does a flagged host mean CVE-2023-32315 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only tries to open a restricted page. Treat a confirmed row as evidence the traversal 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 restricted page, only on hosts already in range. It does not log in or write files.
Does the check need credentials?
No. It fingerprints the public page and reads /login.jsp the way an external scanner would.
What is CVE-2023-32315?
Unauthenticated path traversal in Openfire. CISA listed it on KEV after public exploit and confirmed use. This workflow flags by version, then confirms by opening a restricted page.