CVE-2018-2490
CVE-2018-2490 is a high-severity vulnerability in Sap Fiori Client with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-732.
Key facts
- Severity: High (CVSS 3.x base score 7.8)
- CVSS v2: 6.8
- EPSS exploit prediction: 1% (50th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-732
- Affected product: Sap Fiori Client
- Published:
- Last modified:
Description
The broadcast messages received by SAP Fiori Client are not protected by permissions. SAP Fiori Client version 1.11.5 in Google Play store addresses these issues and users must update to that version.
Frequently asked questions
- What is CVE-2018-2490?
- The broadcast messages received by SAP Fiori Client are not protected by permissions. SAP Fiori Client version 1.11.5 in Google Play store addresses these issues and users must update to that version.
- How severe is CVE-2018-2490?
- CVE-2018-2490 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2018-2490 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2018-2490?
- CVE-2018-2490 affects Sap Fiori Client. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2018-2490?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2018-2490 published?
- CVE-2018-2490 was published on 2018-11-13 and last updated on 2026-06-17.
References
- https://launchpad.support.sap.com/#/notes/2691126
- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=503809832
Affected products (1)
- cpe:2.3:a:sap:fiori_client:*:*:*:*:*:*:*:*
More vulnerabilities in Sap Fiori Client
- CVE-2018-2491 — High (CVSS 7.8): When opening a deep link URL in SAP Fiori Client with log level set to "Debug", the client application logs the URL to…
- CVE-2018-2489 — High (CVSS 7.8): Locally, without any permission, an arbitrary android application could delete the SSO configuration of SAP Fiori…
- CVE-2018-2488 — High (CVSS 7.8): It is possible for a malware application installed on an Android device to send local push notifications with an empty…
- CVE-2018-2485 — High (CVSS 7.7): It is possible for a malicious application or malware to execute JavaScript in a SAP Fiori application. This can…
- CVE-2021-33699 — Medium (CVSS 6.5): Task Hijacking is a vulnerability that affects the applications running on Android devices due to a misconfiguration in…
All CVEs affecting Sap Fiori Client →
Other CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities
- CVE-2026-9508 — Critical (CVSS 10.0): Incorrect permission settings on a critical resource in Suprema BioStar 2 (versions 2.9.3 through 2.9.11) that allow…
- CVE-2025-14988 — Critical (CVSS 10.0): A security issue has been identified in ibaPDA that could allow unauthorized actions on the file system under certain…
- CVE-2025-69426 — Critical (CVSS 10.0): The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating…
- CVE-2025-12004 — Critical (CVSS 10.0): Incorrect Permission Assignment for Critical Resource vulnerability in The Wikimedia Foundation Mediawiki - Lockdown…
- CVE-2014-125121 — Critical (CVSS 10.0): Array Networks vAPV (version 8.3.2.17) and vxAG (version 9.2.0.34) appliances are affected by a privilege escalation…
- CVE-2025-46093 — Critical (CVSS 9.9): LiquidFiles before 4.1.2 supports FTP SITE CHMOD for mode 6777 (setuid and setgid), which allows FTPDrop users to…
Browse all CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities →