# CVE-2020-6781: Improper Certificate Validation in Bosch Smart Home System App for iOS

> Attackers can intercept video content via man-in-the-middle attacks due to improper certificate validation in the Bosch Smart Home iOS app.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qcq5-vfmc-qgpp

## What is CVE-2020-6781?

CVE-2020-6781 is a medium-severity vulnerability in Bosch Smart Home, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Improper certificate validation for certain connections in the Bosch Smart Home System App for iOS prior to version 9.17.1 potentially allows to intercept video contents by performing a man-in-the-middle attack.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Bosch Smart Home.

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

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

## Is CVE-2020-6781 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-6781 is a medium-severity vulnerability in Bosch Smart Home, published on 16 Sep 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-6781 in the wild and no public exploit code.

Affected product: Bosch Smart Home. 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-6781/ (Markdown: https://insights.sbomify.com/CVE-2020-6781/index.md)
```

## Sources

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

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