CVE-2018-2424
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 · uneditedSAP UI5 did not validate user input before adding it to the DOM structure. This may lead to malicious user-provided JavaScript code being added to the DOM that could steal user information. Software components affected are: SAP Hana Database 1.00, 2.00; SAP UI5 1.00; SAP UI5 (Java) 7.30, 7.31, 7.40, 7,50; SAP UI 7.40, 7.50, 7.51, 7.52, and version 2.0 of SAP UI for SAP NetWeaver 7.00
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 confidenceSAP UI5 fails to validate user input before inserting it into the DOM, enabling stored cross-site scripting (XSS) attacks. Attackers can inject malicious JavaScript that executes in victim browsers to steal session tokens, credentials, or other sensitive information.
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= 1.00= 2.00= 2.0= 7.40= 7.50= 7.51= 7.52= 1.00= 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/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 UI5 installationAccess SAP system via SAP Logon, navigate to System > Status > Component Information, or check the SAP UI5 library files in the system directory (typically under /sapmnt/<SID>/sapwebdisp or /usr/sap/<SID>/<instance>/webdisp)Affected if SAP UI5 component is found on the system
-
Determine SAP UI5 versionExecute transaction code SM37 to view system version information, or check the UI5 library version file (manifest.appdescr or the sap-ui-version.json file in the UI5 deployment directory)Affected if Installed version matches: 1.00 (SAP UI5), 7.30/7.31/7.40/7.50 (SAP UI5 Java), or any UI5 component version listed in affected products
-
Identify if user input gets rendered in DOMReview SAP UI5 application code or custom UI5 controls that accept user input. Inspect browser developer tools (Elements tab) to see if user-supplied values appear directly in HTML without encoding, or check the application logs for XSS filter warningsAffected if Application accepts user input and renders it directly into the DOM without visible sanitization or encoding controls
-
Verify XSS mitigation is absentExamine the application source code for output encoding functions (such as encoder.encodeForHTML, or similar escape methods) or check if SAP UI5's built-in data binding with automatic escaping is disabledAffected if User input is inserted into the DOM without encoding/escaping or custom controls bypass standard UI5 security mechanisms
Your environment is affected if SAP UI5 or SAP UI5 Java is installed with any of the affected versions (1.00, 7.30, 7.31, 7.40, 7.50) AND applications render user-supplied input directly into the DOM without proper validation or 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 dataImplement input validation and output encoding/escaping for all user-supplied data before DOM insertion in SAP UI5 components.
- Consultation3.0 h
- Implementation8.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-2424 — 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-2018-2424 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