Cyber Resilience

CVE-2017-12637

Path Traversal in Sap Netweaver Application Server Java 7.50

CISA KEVActive ExploitationEUVD ExploitedPath Traversal
Published
07 August 2017
Modified
22 April 2026
KEV Added
19 March 2025
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.95 99.9th percentile
Risk Priority 84 floored blend · peak EPSS

Summary

CVE-2017-12637 is a high-severity Path Traversal (CWE-22) vulnerability in Sap Netweaver Application Server Java. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 0.1% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The vulnerability is a directory traversal flaw, identified as CVE-2017-12637 and assigned CWE-22, that affects the scheduler/ui/js/ffffffffbca41eb4/UIUtilJavaScriptJS component in SAP NetWeaver Application Server Java 7.5. It carries a CVSS 3.1 score of 7.5 reflecting network-accessible unauthenticated read access with high confidentiality impact.

Remote attackers can exploit the issue by supplying a .. sequence in the query string to retrieve arbitrary files from the server. The flaw was actively exploited in the wild during August 2017.

The issue is tracked under SAP Security Note 2486657 and appears in the CISA Known Exploited Vulnerabilities Catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Directory 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…

more

2486657.

CWE(s)
KEV Date Added
19 March 2025

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2016-3976Same product: Sap Netweaver Application Server Javaboth on KEV
CVE-2018-2380Same vendor: Sapboth on KEV
CVE-2021-38163Same vendor: Sapboth on KEV
CVE-2023-27269Same vendor: Sap
CVE-2023-49058Same vendor: Sap
CVE-2025-42894Same vendor: Sap
CVE-2023-29186Same vendor: Sap
CVE-2023-27501Same vendor: Sap
CVE-2023-27500Same vendor: Sap
CVE-2023-33989Same vendor: Sap

Affected Assets

sap
netweaver application server java
7.50

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References