CVE-2021-3787
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 · uneditedA vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker with local access to obtain the MQTT credentials that could result in unauthorized access to backend Hubble services.
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 · moderate confidenceA vulnerability in Motorola-branded Binatone Hubble Cameras allows an attacker with local access to extract MQTT credentials stored on the device, potentially enabling unauthorized access to backend Hubble services.
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< 03.50.14< 03.40.02< 03.40.00all versions< 03.40.00all versionsall versionsall versionsCVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Identify the camera modelCheck the device label, packaging, or camera system settings to confirm the model is one of: Halo+, Comfort 85 Connect, Mbp3855, Focus 68, Focus 72r, Cn28, Cn50, or Comfort 40 from BinatoneglobalAffected if The camera is any of these models from Binatoneglobal/Motorola Hubble
-
Check the firmware versionAccess the camera settings via the Hubble app or web interface and locate the firmware version information, or SSH into the device and run: cat /etc/version or cat /proc/versionAffected if The firmware version is lower than 03.50.14 (Halo+), 03.40.02 (Comfort 85 Connect), or 03.40.00 (Mbp3855, Focus 72r), OR if the model is Focus 68, Cn28, Cn50, or Comfort 40 (all versions affected)
-
Verify if MQTT client is configuredCheck the camera configuration files for MQTT settings by examining /etc/mqtt.conf, /etc/config/mqtt, or similar configuration files accessible via the device filesystemAffected if MQTT credentials (username, password, broker address) are stored on the device in plaintext or easily extractable format
-
Confirm physical access vectorReview physical security controls around the camera to determine if an attacker could gain direct access to the device or its storageAffected if The camera is deployed in an area where unauthorized physical access is plausible
A user is affected if they operate any of the listed Binatoneglobal Hubble camera models with firmware versions below the specified thresholds, or Focus 68, Cn28, Cn50, or Comfort 40 at any version, and the device stores MQTT credentials accessible via local access.
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.
dbcve · scoped03.40.0003.40.0203.50.14
Restrict physical access to affected cameras, rotate exposed MQTT credentials, apply any available firmware updates from the vendor, and monitor MQTT traffic for unauthorized access.
Firmware version 03.50.14 for Halo+; 03.40.02 for Comfort 85 Connect; 03.40.00 for Mbp3855 and Focus 72r; contact vendor for fixes to Focus 68, Cn28, Cn50, Comfort 40 (all versions affected)
- 1. Identify the specific camera model from the affected product list (Halo+, Comfort 85 Connect, Mbp3855, Focus 68, Focus 72r, Cn28, Cn50, or Comfort 40)
- 2. Determine the current firmware version of the camera (typically found in the device settings or administration web interface)
- 3. Download the latest firmware from binatoneglobal.com, ensuring the version meets or exceeds the fixed release: Halo+ Camera to 03.50.14, Comfort 85 Connect to 03.40.02, Mbp3855 to 03.40.00, Focus 72r to 03.40.00
- 4. Follow the manufacturer's firmware update procedure (usually via web UI or SD card update)
- 5. After updating, verify the new firmware version is applied and confirm the MQTT credentials are no longer stored in plaintext
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3787 — 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-2021-3787 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