# CVE-2020-6196: Denial of service in SAP BusinessObjects Mobile (MobileBIService)

> An attacker can cause a Denial of Service in SAP BusinessObjects Mobile by generating multiple requests to block all threads.

- **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:** 10 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-g96m-w74g-mqcv

## What is CVE-2020-6196?

CVE-2020-6196 is a high-severity denial of service vulnerability in SAP BusinessObjects Mobile (MobileBIService), published on 10 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SAP BusinessObjects Mobile (MobileBIService), version 4.2, allows an attacker to generate multiple requests, using which he can block all the threads resulting in a Denial of Service.

## Which versions are affected by CVE-2020-6196?

It affects 1 product.


Products: Sap Businessobjects Mobile.

## How do I fix CVE-2020-6196?

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

## Is CVE-2020-6196 being exploited?

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

## Other vulnerabilities in SAP BusinessObjects Mobile (MobileBIService)

- [CVE-2019-0240](https://insights.sbomify.com/CVE-2019-0240/): Denial of service in SAP Business Objects Mobile for Android (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6196 and fix it if it is affected.

What it is: CVE-2020-6196 is a high-severity denial of service vulnerability in SAP BusinessObjects Mobile (MobileBIService), published on 10 Mar 2020. 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-2020-6196 in the wild and no public exploit code.

Affected product: SAP BusinessObjects Mobile (MobileBIService). 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-2020-6196/ (Markdown: https://insights.sbomify.com/CVE-2020-6196/index.md)
```

## Sources

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

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