Point hosts at Check Point Quantum and flag CVE-2024-24919 (info disclosure) by version, then confirm with a public MyCRL GET. Non-destructive. CISA KEV.
Reads the public MyCRL path on flagged hosts. Advisory
Detect
Fingerprints Quantum and flags CVE-2024-24919 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 Check Point Quantum Security Gateways and sorts each host by whether its version falls in the CVE-2024-24919 range. A Quantum gateway is the perimeter. CVE-2024-24919 is information disclosure that CISA put on KEV after public use. A forgotten R81 box on a lab VLAN still answers the same 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 Check Point), 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-2024-24919 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only GETs the public MyCRL path. 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 Check Point Quantum Security Gateways 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 GET of the public MyCRL path.
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 the public MyCRL path, and only after the version flag.
Outputs
results.jsonl. One row per host: URL, whether Check Point Quantum Security Gateways was detected, the version read, the affected flag, and whether the public MyCRL 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) the public MyCRL path.
Sample output
The records below are illustrative and do not come from a real run. They show one Check Point Quantum Security Gateways host inside the CVE-2024-24919 range, one patched host, and one host that is not the product.
Which Check Point Quantum Security Gateways versions does this flag?
R80.20, R80.40, R81, R81.10, and R81.20 as exact matches in the check. Any build the check does not list as an exact R80 or R81 hit is the floor the graph treats as not affected. The compare uses the version the product itself served.
Does a flagged host mean CVE-2024-24919 was exploited?
No. A flagged row is patch-lag against the range table. Confirm only tries to GET the public MyCRL path. Treat a confirmed row as evidence that path 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 the public MyCRL path, 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-2024-24919?
Information disclosure on Check Point Quantum Security Gateways. CISA listed it on KEV after public use. This workflow flags by version, then confirms with a public MyCRL GET.