# CVE-2018-2500: Information disclosure in SAP Mobile Secure for Android

> An attacker can access restricted information in the SAP Mobile Secure Android client, potentially exposing sensitive data to unauthorized users.

- **Severity:** Medium 4.7 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3425-8q76-vpj9

## What is CVE-2018-2500?

CVE-2018-2500 is a medium-severity vulnerability in SAP Mobile Secure for Android, published on 11 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2018-2500?

It affects 1 product.


Products: Sap Mobile Secure.

## How do I fix CVE-2018-2500?

No fix has been published for CVE-2018-2500 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-2500 being exploited?

There is no known exploitation of CVE-2018-2500 in the wild and no public exploit code.

## Other vulnerabilities in SAP Mobile Secure for Android

- [CVE-2018-2482](https://insights.sbomify.com/CVE-2018-2482/): Denial of service in SAP Mobile Secure Android Application (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-2500 and fix it if it is affected.

What it is: CVE-2018-2500 is a medium-severity vulnerability in SAP Mobile Secure for Android, published on 11 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-2500 in the wild and no public exploit code.

Affected product: SAP Mobile Secure for Android. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-2500/ (Markdown: https://insights.sbomify.com/CVE-2018-2500/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-2500
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-2500
- OSV: https://osv.dev/vulnerability/CVE-2018-2500

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-2500/
Summaries are generated and may contain mistakes; the official description above is the record.