dbcve.org
Halo\+ Camera FirmwareOperating system · Binatoneglobal

CVE-2021-3791

MEDIUM · 6.5 CVSS v3.1 Published 2021-11-12
Fix available
A fix is available. Upgrade to 03.40.00 / 03.40.02 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
An information disclosure vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an unauthenticated attacker on the same subnet to download an encrypted log file containing sensitive information such as WiFi SSID and password.

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 confidence

This vulnerability allows unauthenticated attackers on the same network subnet to download an encrypted log file from affected Motorola-branded Binatone Hubble Cameras. The log file contains sensitive information including WiFi SSID and password credentials, exposing network credentials to anyone with local network access.

MitigationNetwork segmentation should be implemented to isolate IoT devices from sensitive network segments. Contact Binatone/Motorola for available firmware updates that address this authentication bypass.

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
Halo\+ Camera FirmwareOperating system
Affected:< 03.50.14
Comfort 85 Connect FirmwareOperating system
Affected:< 03.40.02
Mbp3855 FirmwareOperating system
Affected:< 03.40.00
Focus 68 FirmwareOperating system
Affected:all versions
Focus 72r FirmwareOperating system
Affected:< 03.40.00
Cn28 FirmwareOperating system
Affected:all versions
Cn50 FirmwareOperating system
Affected:all versions
Comfort 40 FirmwareOperating system
Affected:all versions

CVSS 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
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Check the device label or access the web interface to confirm the exact model name (e.g., Halo+, Comfort 85 Connect, Mbp3855, Focus 68, Focus 72r, Cn28, Cn50, Comfort 40)
    Affected if The device is a Binatoneglobal Halo+, Comfort 85 Connect, Mbp3855, Focus 68, Focus 72r, Cn28, Cn50, or Comfort 40 camera
  2. Check the firmware version
    Access the camera's web interface or API and navigate to the settings or system information page to find the installed firmware version
    Affected if The firmware version is lower than 03.50.14 (Halo+), 03.40.02 (Comfort 85 Connect), 03.40.00 (Mbp3855, Focus 72r), or any version for Focus 68, Cn28, Cn50, Comfort 40 (all versions affected)
  3. Verify network accessibility
    Confirm the camera is accessible on the network from other devices on the same subnet. Attempt to access the device from a different host on the local network
    Affected if The camera is reachable from other devices on the same network subnet without authentication

If the device is one of the affected Binatoneglobal camera models and the firmware version falls within the vulnerable ranges listed, the device is likely affected by this unauthenticated log file disclosure vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 03.40.00 / 03.40.02 / 03.50.14 or later
Fixed in 03.40.0003.40.0203.50.14
Interim mitigation

Network segmentation should be implemented to isolate IoT devices from sensitive network segments. Contact Binatone/Motorola for available firmware updates that address this authentication bypass.

Recommended fix Moderate confidence

Halo+ to 03.50.14, Comfort 85 Connect to 03.40.02, Mbp3855 to 03.40.00, Focus 72r to 03.40.00

  1. Identify the specific camera model from the affected product list
  2. Determine the current firmware version of the camera through its web interface or mobile app
  3. Navigate to binatoneglobal.com and locate the firmware download section for Motorola Hubble cameras
  4. Download the appropriate firmware version: Halo+ to 03.50.14, Comfort 85 Connect to 03.40.02, Mbp3855 to 03.40.00, Focus 72r to 03.40.00
  5. Access the camera's administration interface and locate the firmware update section
  6. Upload and apply the new firmware version following the on-screen instructions
  7. Verify the firmware update was successful by checking the new version number
  8. After update, verify the vulnerability is resolved by confirming log files no longer contain WiFi credentials
Caveat For models with no fixed version listed (Focus 68, Cn28, Cn50, Comfort 40), no firmware upgrade is available from vendor

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Halo\+ Camera Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3791 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-3791 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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