CVE-2019-0240
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 · uneditedSAP Business Objects Mobile for Android (before 6.3.5) application allows an attacker to provide malicious input in the form of a SAP BI link, preventing legitimate users from accessing the application by crashing it.
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 confidenceSAP Business Objects Mobile for Android (versions before 6.3.5) contains a denial-of-service vulnerability where processing a specially crafted malicious SAP BI link causes the application to crash, rendering it unavailable to legitimate users. The vulnerability stems from insufficient input validation when handling SAP BI links.
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< 6.3.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify SAP Business Objects Mobile is installed on Android deviceNavigate to Settings > Apps on the Android device and search for 'SAP BusinessObjects Mobile' or 'BusinessObjects Mobile' in the installed apps listAffected if The application is not found in the app list, meaning the app is not installed and this CVE does not apply
-
Determine the installed version numberTap on the SAP BusinessObjects Mobile app entry in Settings > Apps, then locate the 'Version' or 'App version' field displayed under the app nameAffected if No version number is displayed or the app cannot be located in the app list
-
Compare installed version against affected rangeCompare the version number found in the previous step to the affected range: any version below 6.3.5 (for example, 6.3.4, 6.3.0, 5.x, 4.x) is within the vulnerable rangeAffected if The installed version is a release prior to 6.3.5, such as 6.3.4, 6.3.3, or any earlier major or minor release
-
Confirm the app handles SAP BI linksOpen the application and check if it is configured to open or process SAP BI (Business Intelligence) links, typically found in app settings or preferences under link handling optionsAffected if The app processes SAP BI links and the version is below 6.3.5
The environment is affected if SAP Business Objects Mobile for Android is installed with a version number lower than 6.3.5 and the app is used to handle SAP BI links.
Generated from the published advisory. Verify against your own configuration.
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 data6.3.5
Upgrade SAP Business Objects Mobile for Android to version 6.3.5 or later. If upgrading is not possible, implement input validation and sanitization for SAP BI links at a proxy or MDM level to block malicious links before they reach the application.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0240 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0240 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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