dbcve.org
Halo\+ Camera FirmwareOperating system · Binatoneglobal

CVE-2021-3577

HIGH · 8.8 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 →
93/100
Remediation priority · Urgent
High EPSS 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 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.

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

An unauthenticated remote code execution vulnerability in Motorola-branded Binatone Hubble Cameras allows attackers on the same local network to gain unauthorized access and execute arbitrary code without any credentials.

MitigationIsolate affected devices on a separate VLAN or restricted network segment, apply any available vendor firmware updates, and disable unnecessary remote access features if the device supports such configuration.

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
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/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 checks

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

  1. Identify the camera model
    Locate the device label or check the Hubble app/web interface for the exact model name (e.g., Halo+, Comfort 85 Connect, Mbp3855, Focus 68, Focus 72r, Cn28, Cn50, Comfort 40)
    Affected if The device model matches any Binatoneglobal camera listed in the affected products
  2. Determine the firmware version
    Access the camera's web interface or Hubble mobile app and navigate to Settings > Device Info > Firmware Version, or check the label on the device packaging
    Affected if The installed firmware version falls below the safe threshold for your model (Halo+ < 03.50.14, Comfort 85 Connect < 03.40.02, Mbp3855 < 03.40.00, Focus 72r < 03.40.00) or is any version for Focus 68, Cn28, Cn50, Comfort 40
  3. Verify network accessibility
    Confirm the camera is connected to your local network and is reachable from other devices on the same subnet (e.g., ping the camera IP or check router device list)
    Affected if The camera is accessible from other devices on the local network
  4. Check for unauthenticated service exposure
    Attempt to access common camera management ports (typically HTTP on 80/8080) from a different device on the same network without providing any login credentials
    Affected if The camera web interface or API responds without requiring authentication

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

Isolate affected devices on a separate VLAN or restricted network segment, apply any available vendor firmware updates, and disable unnecessary remote access features if the device supports such configuration.

Recommended fix High confidence

Upgrade to fixed firmware releases: Halo+ Camera 03.50.14, Comfort 85 Connect 03.40.02, Mbp3855 03.40.00, Focus 72r 03.40.00; contact vendor for Focus 68, Cn28, Cn50, Comfort 40

  1. Identify the specific camera model from the affected product list
  2. Check the current firmware version on the device through the web interface or mobile app
  3. Navigate to binatoneglobal.com and locate the support or firmware download section for your camera model
  4. Download the appropriate fixed firmware version: Halo+ Camera to 03.50.14, Comfort 85 Connect to 03.40.02, Mbp3855 to 03.40.00, Focus 72r to 03.40.00
  5. Follow the vendor-provided firmware upgrade instructions, typically via the web interface or SD card method
  6. Verify the firmware version has been successfully updated after the upgrade process
  7. For models with 'all versions' affected (Focus 68, Cn28, Cn50, Comfort 40), contact Binatone support directly for available firmware updates or remediation guidance
Caveat Review release notes for any functionality changes; ensure stable power during firmware update to avoid device brickage

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

Fix this in Halo\+ Camera Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-3577 — 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-3577 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