# CVE-2018-2482: Denial of service in SAP Mobile Secure Android Application

> An attacker can cause a denial of service in the SAP Mobile Secure Android client, preventing legitimate users from accessing the service.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-99p2-64gx-4vg3

## What is CVE-2018-2482?

CVE-2018-2482 is a high-severity denial of service vulnerability in SAP Mobile Secure Android Application, published on 13 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

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

It affects 1 product.


Products: Sap Mobile Secure.

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

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

## Is CVE-2018-2482 being exploited?

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

## Other vulnerabilities in SAP Mobile Secure Android Application

- [CVE-2018-2500](https://insights.sbomify.com/CVE-2018-2500/): Information disclosure in SAP Mobile Secure for Android (medium 4.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-2482 is a high-severity denial of service vulnerability in SAP Mobile Secure Android Application, published on 13 Nov 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-2482 in the wild and no public exploit code.

Affected product: SAP Mobile Secure Android Application. 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-2482/ (Markdown: https://insights.sbomify.com/CVE-2018-2482/index.md)
```

## Sources

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

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