What is the severity of CVE-2018-2500?

CVE-2018-2500 is rated as medium severity due to its potential to expose sensitive information.

How do I fix CVE-2018-2500?

To fix CVE-2018-2500, upgrade the SAP Mobile Secure Android client to version 6.60.19942.0 SP28 1711 or later.

Which versions of SAP Mobile Secure are affected by CVE-2018-2500?

CVE-2018-2500 affects SAP Mobile Secure Android clients before version 6.60.19942.0 SP28 1711.

What kind of information can be accessed due to CVE-2018-2500?

CVE-2018-2500 allows unauthorized access to restricted information within the SAP Mobile Secure Android client.

Is there a workaround for CVE-2018-2500?

There are no known effective workarounds for CVE-2018-2500, so upgrading to a patched version is recommended.

Vulnerability/
CVE-2018-2500

medium

4.7

11/12/2018

5/8/2024

CVE-2018-2500

First published: Tue Dec 11 2018(Updated: )

Under certain conditions SAP Mobile Secure Android client (before version 6.60.19942.0 SP28 1711) allows an attacker to access information which would otherwise be restricted.

Credit: cna@sap.com

Affected Software	Affected Version	How to fix
SAP Mobile Secure Android	<=6.60.19942.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2018-2500?
CVE-2018-2500 is rated as medium severity due to its potential to expose sensitive information.
How do I fix CVE-2018-2500?
To fix CVE-2018-2500, upgrade the SAP Mobile Secure Android client to version 6.60.19942.0 SP28 1711 or later.
Which versions of SAP Mobile Secure are affected by CVE-2018-2500?
CVE-2018-2500 affects SAP Mobile Secure Android clients before version 6.60.19942.0 SP28 1711.
What kind of information can be accessed due to CVE-2018-2500?
CVE-2018-2500 allows unauthorized access to restricted information within the SAP Mobile Secure Android client.
Is there a workaround for CVE-2018-2500?
There are no known effective workarounds for CVE-2018-2500, so upgrading to a patched version is recommended.

collector/nvd-index
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/references
agent/severity
agent/author
agent/description
agent/event
agent/tags
agent/source
vendor/sap
canonical/sap mobile secure android
version/sap mobile secure android/6.60.19942.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2018-2500?
CVE-2018-2500 is rated as medium severity due to its potential to expose sensitive information.
How do I fix CVE-2018-2500?
To fix CVE-2018-2500, upgrade the SAP Mobile Secure Android client to version 6.60.19942.0 SP28 1711 or later.
Which versions of SAP Mobile Secure are affected by CVE-2018-2500?
CVE-2018-2500 affects SAP Mobile Secure Android clients before version 6.60.19942.0 SP28 1711.
What kind of information can be accessed due to CVE-2018-2500?
CVE-2018-2500 allows unauthorized access to restricted information within the SAP Mobile Secure Android client.
Is there a workaround for CVE-2018-2500?
There are no known effective workarounds for CVE-2018-2500, so upgrading to a patched version is recommended.