# CVE-2019-7728: Weak cryptography in n/a

> Improper TLS certificate validation in the Android app allows attackers to perform man-in-the-middle attacks on connections.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 22 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c78c-fx8f-9542

## What is CVE-2019-7728?

CVE-2019-7728 is a high-severity vulnerability in n/a, published on 22 Feb 2019. 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

An issue was discovered in the Bosch Smart Camera App before 1.3.1 for Android. Due to improperly implemented TLS certificate checks, a malicious actor could potentially succeed in executing a man-in-the-middle attack for some connections. (The Bosch Smart Home App is not affected. iOS Apps are not affected.)

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2019-7728?

It affects 1 product.


Products: Bosch Smart Camera.

## How do I fix CVE-2019-7728?

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

## Is CVE-2019-7728 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7729](https://insights.sbomify.com/CVE-2019-7729/): Information disclosure in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7728 and fix it if it is affected.

What it is: CVE-2019-7728 is a high-severity vulnerability in n/a, published on 22 Feb 2019. 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-2019-7728 in the wild and no public exploit code.

Affected product: n/a. 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-2019-7728/ (Markdown: https://insights.sbomify.com/CVE-2019-7728/index.md)
```

## Sources

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

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