# CVE-2021-3577: Command injection in Binatone Hubble Cameras

> Unauthenticated attackers on the same network can execute arbitrary code on Motorola Binatone Hubble Cameras due to improper authorization and command injection flaws.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-794m-w426-mg5p

## What is CVE-2021-3577?

CVE-2021-3577 is a high-severity command injection vulnerability in Motorola Binatone Hubble Cameras, published on 12 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An unauthenticated remote code execution vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker on the same network unauthorized access to the device.

Weakness: CWE-863 (Incorrect Authorization), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2021-3577?

It affects 21 products.


Products: Binatoneglobal Cn28 Firmware, Binatoneglobal Cn40 Firmware, Binatoneglobal Cn50 Firmware, Binatoneglobal Cn75 Firmware, Binatoneglobal Comfort 40 Firmware, Binatoneglobal Comfort 50 Connect Firmware, Binatoneglobal Comfort 85 Connect Firmware, Binatoneglobal Connect 20 Firmware, Binatoneglobal Connect View 65 Firmware, Binatoneglobal Ease44 Firmware, Binatoneglobal Focus 68 Firmware, Binatoneglobal Focus 72r Firmware, Binatoneglobal Halo\+ Camera Firmware, Binatoneglobal Lux 64 Firmware, Binatoneglobal Lux 65 Firmware, Binatoneglobal Lux 85 Connect Firmware, Binatoneglobal Mbp3667 Firmware, Binatoneglobal Mbp3855 Firmware, Binatoneglobal Mbp4855 Firmware, Binatoneglobal Mbp669 Connect Firmware and 1 more.

## How do I fix CVE-2021-3577?

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

## Is CVE-2021-3577 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3577 exists.

Public exploit code:

- Motorola Baby Monitors - Remote Command Execution (nuclei): http/cves/2021/CVE-2021-3577.yaml

## Other vulnerabilities in Motorola Binatone Hubble Cameras

- [CVE-2021-3788](https://insights.sbomify.com/CVE-2021-3788/): Auth bypass in Binatone Hubble Cameras (medium 6.8)
- [CVE-2021-3790](https://insights.sbomify.com/CVE-2021-3790/): Memory corruption in Binatone Hubble Cameras (medium 6.5)
- [CVE-2021-3791](https://insights.sbomify.com/CVE-2021-3791/): Information disclosure in Binatone Hubble Cameras (medium 6.5)
- [CVE-2021-3793](https://insights.sbomify.com/CVE-2021-3793/): Missing authorization in Binatone Hubble Cameras (medium 6.5)
- [CVE-2021-3787](https://insights.sbomify.com/CVE-2021-3787/): Information disclosure in Binatone Hubble Cameras (medium 6.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-3577 and fix it if it is affected.

What it is: CVE-2021-3577 is a high-severity command injection vulnerability in Motorola Binatone Hubble Cameras, published on 12 Nov 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-3577 exists.

Affected product: Motorola Binatone Hubble Cameras. 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-2021-3577/ (Markdown: https://insights.sbomify.com/CVE-2021-3577/index.md)
```

## Sources

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

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