CVE-2017-12637
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectory traversal vulnerability in scheduler/ui/js/ffffffffbca41eb4/UIUtilJavaScriptJS in SAP NetWeaver Application Server Java 7.5 allows remote attackers to read arbitrary files via a .. (dot dot) in the query string, as exploited in the wild in August 2017, aka SAP Security Note 2486657.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDirectory traversal vulnerability in SAP NetWeaver AS Java 7.5 scheduler UI component allows remote attackers to read arbitrary files via .. (dot dot) sequences in the query string of the UIUtilJavaScriptJS endpoint.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.50CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify SAP NetWeaver AS Java versionAccess the SAP NetWeaver Administrator or use transaction SM51 to view the installed release version. Alternatively, check the system info via the SAP Management Console or query the kernel version using the SAP kernel executables.Affected if The installed version is exactly 7.50 (SAP NetWeaver AS Java 7.5)
-
Verify scheduler application is deployedCheck if the SAP Scheduler application is installed by accessing the SAP NetWeaver Administrator and navigating to Applications or use transaction SE16 to query table WD应用程序 (or check via SDM/SLM).Affected if The scheduler application is deployed and running on the system
-
Confirm vulnerable endpoint is accessibleAttempt to access the URL pattern: /scheduler/ui/js/UIUtilJavaScriptJS on your SAP NetWeaver AS Java host. For example: http://<host>:<port>/scheduler/ui/js/UIUtilJavaScriptJSAffected if The endpoint returns a response (200 OK) rather than a 404 error, indicating the scheduler UI is accessible
-
Test for directory traversal vulnerabilitySend a crafted request to the endpoint with path traversal sequences, such as: /scheduler/ui/js/UIUtilJavaScriptJS?/..//..//..//..//windows/win.ini or /scheduler/ui/js/UIUtilJavaScriptJS?/..//..//..//..//etc/passwdAffected if The response contains contents of the requested arbitrary file (win.ini, passwd, etc.) confirming the directory traversal is exploitable
Your environment is affected if you are running SAP NetWeaver AS Java version 7.50, the scheduler UI component is deployed, and the /scheduler/ui/js/UIUtilJavaScriptJS endpoint is accessible and responds with arbitrary file contents to traversal payloads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply SAP Security Note 2486657 immediately. Until patch is available, consider network-level blocking of the affected scheduler/ui/js/ path or disabling the scheduler application if not required.
SAP NetWeaver Application Server Java 7.50 with Security Note 2486657 applied (or upgrade to later supported version if available)
- 1. Obtain SAP Security Note 2486657 from the SAP Support Portal (support.sap.com)
- 2. Review the security note for the specific patch/instructions for SAP NetWeaver Application Server Java 7.50
- 3. Apply the patch according to SAP's standard security update procedures
- 4. After patching, verify the vulnerability is resolved by attempting the original path traversal request (scheduler/ui/js/ffffffffbca41eb4/UIUtilJavaScriptJS?..%2F..%2F) and confirming it is blocked
- 5. Ensure the SAP system is restarted if required by the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12637 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12637 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data