dbcve.org
Fiori ClientApplication · Sap

CVE-2018-2491

HIGH · 7.8 CVSS v3.0 Published 2018-11-13
Fix available
A fix is available. Upgrade to 1.11.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
When opening a deep link URL in SAP Fiori Client with log level set to "Debug", the client application logs the URL to the log file. If this URL contains malicious JavaScript code it can eventually run inside the built-in log viewer of the application in case user opens the viewer and taps on the hyperlink in the viewer. SAP Fiori Client version 1.11.5 in Google Play store addresses these issues and users must update to that version.

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 confidence

SAP Fiori Client logs deep link URLs to a file when debug logging is enabled. If a malicious JavaScript payload is embedded in the URL, it gets stored in the log and executes when the user opens the built-in log viewer and taps on the hyperlink - a stored XSS vulnerability.

MitigationUpdate SAP Fiori Client to version 1.11.5 or later from the Google Play store to remediate this vulnerability.

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
Fiori ClientApplication
Affected:< 1.11.5

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed SAP Fiori Client version
    On the Android device, go to Settings > Apps > SAP Fiori Client and view the version information. Compare the version number to 1.11.5.
    Affected if Version is below 1.11.5
  2. Verify debug logging status
    In the SAP Fiori Client app, navigate to Settings or About to determine if debug logging or diagnostics logging is enabled. This is typically found under advanced settings or logging options.
    Affected if Debug logging is enabled in the application settings
  3. Examine application log files
    Access the device's internal storage or app data directory for SAP Fiori Client log files. On Android, this is typically found in /data/data/com.sap.fiori.client/logs/ or accessible via ADB. Inspect log files for stored deep link URLs.
    Affected if Log files exist and contain deep link URLs that could contain malicious JavaScript payloads

A user is affected if their SAP Fiori Client version is below 1.11.5 AND debug logging is enabled, creating stored XSS risk in the log viewer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 1.11.5 or later
Fixed in 1.11.5
Interim mitigation

Update SAP Fiori Client to version 1.11.5 or later from the Google Play store to remediate this vulnerability.

Fix this in Fiori Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2491 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-2491 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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