CVE

NetWeaver Path Traversal (CVE-2017-12637)

Point hosts at SAP NetWeaver and flag CVE-2017-12637 (path traversal) from a version compare, then confirm with a public static file read. Non-destructive.

AuthorTrickest
100%

Notes on this workflow

Collect

Merges per-host detect and confirm rows.

Confirm

Reads a public static file through the known traversal. Advisory

Detect

Fingerprints NetWeaver and flags CVE-2017-12637 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 SAP NetWeaver and sorts each host by whether its version falls in the CVE-2017-12637 range. NetWeaver portals outlive the team that stood them up. CVE-2017-12637 is path traversal that CISA still lists on KEV. The check fingerprints an SAP title and flags exactly 7.50, which is the train the graph encodes. Give it hostnames, IP addresses, or URLs you are authorised to test. The workflow fingerprints the product from the public page (title match on SAP), 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-2017-12637 is on CISA KEV (known exploited). Version flag is first. Hosts in range get a second node that only reads a public static file through the known traversal. It does not read 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

  1. Read the target list. Hosts, URLs, or ranges, one per line, become the scope.
  2. Fingerprint each host as SAP NetWeaver 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.
  3. Confirm only those flagged hosts by reading a public static file through the known traversal.
  4. Collect the per-host rows: product match, version, affected flag, confirmed flag, and any fetch error.
  5. 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 static file, and only after the version flag.

Outputs

  • results.jsonl. One row per host: URL, whether SAP NetWeaver was detected, the version read, the affected flag, and whether the public-file 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 static file.

Sample output

The records below are illustrative and do not come from a real run. They show one SAP NetWeaver host inside the CVE-2017-12637 range, one patched host, and one host that is not the product.

target_urlproduct_detectedversionaffectederror
https://sap-a.example.comtrue7.50truenull
https://sap-b.example.orgtrue7.52falsenull
https://shop.example.netfalsenullfalsenot_product
{"cve": "CVE-2017-12637", "total_targets": 3, "affected": 1, "not_affected": 1, "errors": 1}

FAQ

Which SAP NetWeaver versions does this flag?

exactly 7.50 in the check table. any build the check does not match as 7.50 is the floor the graph treats as not affected. The compare uses the version the product itself served.

Does a flagged host mean CVE-2017-12637 was exploited?

No. A flagged row is patch-lag against the range table. Confirm only tries to read a public static file. 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 public static file, 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-2017-12637?

Path traversal in SAP NetWeaver. CISA listed it on KEV. The check flags exactly version 7.50. This workflow flags by version, then confirms with a public-file read.

Get a personalized demo

See Trickest in Action

A 30-minute walkthrough. We map the platform to your stack and answer pricing and deployment questions for your environment.