dbcve.org
Mobile SecureApplication · Sap

CVE-2018-2482

HIGH · 7.5 CVSS v3.0 Published 2018-11-13
Fix available
A fix is available. Upgrade to 6.60.19942.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SAP Mobile Secure Android Application (Mobile-secure.apk) before version 6.60.19942.0 contains a denial of service vulnerability that allows an attacker to crash the service or flood it, preventing legitimate users from accessing the service.

MitigationUpgrade SAP Mobile Secure Android client to version 6.60.19942.0 or later (released Mid-October 2018).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mobile SecureApplication
Affected:< 6.60.19942.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check SAP Mobile Secure app version in Android Settings
    Open Android Settings > Apps > SAP Mobile Secure > App info. Look for 'Version' or 'Version name' field.
    Affected if Version displayed is less than 6.60.19942.0
  2. Check version via Google Play Store listing
    Open Play Store, search for 'SAP Mobile Secure', tap on the app. The version number appears under the app title.
    Affected if Version shown is less than 6.60.19942.0
  3. Inspect APK file version metadata
    If you have the APK file (Mobile-secure.apk), use an APK inspector tool or run 'aapt dump badging Mobile-secure.apk' to extract the versionName and versionCode.
    Affected if versionName is lower than 6.60.19942.0 or versionCode is lower than 19942
  4. Verify app is actually the vulnerable component
    Confirm the app in question is SAP Mobile Secure Android client and not a different SAP mobile product.
    Affected if The installed app is SAP Mobile Secure (Mobile-secure.apk) and version is below 6.60.19942.0

You are affected if SAP Mobile Secure Android application is installed with any version lower than 6.60.19942.0.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.60.19942.0 or later
Fixed in 6.60.19942.0
Interim mitigation

Upgrade SAP Mobile Secure Android client to version 6.60.19942.0 or later (released Mid-October 2018).

Fix this in Mobile Secure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-2482 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-2482 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data