dbcve.org
Fiori ClientApplication · Sap

CVE-2018-2489

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
Locally, without any permission, an arbitrary android application could delete the SSO configuration of SAP Fiori Client. 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

In SAP Fiori Client versions prior to 1.11.5, an arbitrary Android application installed locally on the device could delete the SSO (Single Sign-On) configuration without requiring any permissions. This indicates a critical access control flaw where the application's local storage or shared preferences containing SSO settings were improperly protected, allowing any app to modify or remove these sensitive configuration files.

MitigationUsers must update SAP Fiori Client to version 1.11.5 or later from the Google Play Store. Organizations should also verify that all managed devices have the updated version installed and confirm SSO functionality is operational post-update.

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. Verify SAP Fiori Client is installed
    On the Android device, go to Settings > Apps > Apps list and search for 'SAP Fiori Client', or run 'adb shell pm list packages | grep fiori' to list installed packages
    Affected if If the package 'com.sap.fiori.client' or 'com.sap.fioriclient' appears in the package list, the app is installed
  2. Determine the installed version
    In Settings > Apps > SAP Fiori Client > App info, view the Version number displayed under the app name. Alternatively, run 'adb shell dumpsys package com.sap.fiori.client | grep versionName'
    Affected if If a version number is displayed, record it for the next comparison step
  3. Compare version against vulnerability threshold
    Compare the installed version number to 1.11.5. Version numbers follow semantic versioning where each numeric segment is compared left to right (e.g., 1.10.0 < 1.11.0 < 1.11.5)
    Affected if If the installed version is less than 1.11.5 (such as 1.11.4, 1.10.0, 1.9.0, etc.), the device is vulnerable to this CVE
  4. Confirm SSO configuration exposure
    This vulnerability allows any app to delete SSO settings without permissions. On affected versions, the shared preferences or local storage containing SSO tokens (typically stored in /data/data/com.sap.fiori.client/shared_prefs/ or files/ directory) could be modified or removed by other installed applications
    Affected if If the installed version is below 1.11.5 and the device has SSO credentials configured for Fiori apps, those credentials may have been accessible to other applications

The environment is affected if SAP Fiori Client for Android is installed at a version lower than 1.11.5, as this version threshold is the boundary where the improper access control on SSO configuration was fixed.

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

Users must update SAP Fiori Client to version 1.11.5 or later from the Google Play Store. Organizations should also verify that all managed devices have the updated version installed and confirm SSO functionality is operational post-update.

Fix this in Fiori Client Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2489 — 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-2489 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