CVE-2019-0337
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 · uneditedJava Proxy Runtime of SAP NetWeaver Process Integration, versions 7.10, 7.11, 7.30, 7.31, 7.40, 7.50, does not sufficiently encode user-controlled inputs and allows an attacker to execute malicious scripts in the url thereby resulting in Reflected Cross-Site Scripting (XSS) vulnerability
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 confidenceReflected XSS vulnerability in the Java Proxy Runtime of SAP NetWeaver Process Integration allows attackers to inject malicious scripts via unsanitized URL parameters. When users click crafted links, the unencoded input is reflected back and executed in their browsers.
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.10= 7.11= 7.30= 7.31= 7.40= 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Process Integration installationLocate the SAP NetWeaver installation directory and identify the PI/XI component. Common paths include /usr/sap/<SID>/<instance> on Unix or C:\usr\sap\<SID>\<instance> on Windows. Look for PI or XI-related modules.Affected if The product is not installed or is a different product altogether (not NetWeaver Process Integration)
-
Determine the installed NetWeaver PI versionUse SAP transaction code SM51 to view the release version, or check the installed software component versions via SAP Solution Manager or the SAP Installed Software catalog. The version will be displayed as 7.10, 7.11, 7.30, 7.31, 7.40, or 7.50.Affected if The installed version matches exactly 7.10, 7.11, 7.30, 7.31, 7.40, or 7.50
-
Verify Java Proxy Runtime is enabledAccess the SAP NetWeaver Administrator (NWA) or SAP Management Console. Navigate to the Java Proxy Runtime configuration area under the Integration Directory or Runtime. Confirm whether the Java Proxy Runtime service is active and accessible.Affected if Java Proxy Runtime is enabled and accessible via HTTP/HTTPS endpoints
-
Test for reflected XSS in URL parametersAccess the Java Proxy Runtime endpoint and attempt to inject a benign test string such as <script>alert(1)</script> in URL parameters. Use a web proxy to capture the response and verify whether the input is reflected back without HTML encoding.Affected if The unsanitized input is reflected in the response and would execute in a user browser
A user is affected if they have SAP NetWeaver Process Integration version 7.10, 7.11, 7.30, 7.31, 7.40, or 7.50 with the Java Proxy Runtime enabled and accessible, and the URL parameters are reflected without encoding.
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.
From vendor dataApply the relevant SAP security patch for CVE-2019-0337. Until patched, consider deploying a WAF rule to filter malicious URL patterns and educate users not to click untrusted links.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0337 — 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-2019-0337 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