CVE-2021-3790
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 buffer overflow was reported in the local web server of some Motorola-branded Binatone Hubble Cameras that could allow an unauthenticated attacker on the same network to perform a denial-of-service attack against 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 confidenceA buffer overflow vulnerability exists in the local web server component of Motorola-branded Binatone Hubble Cameras. An unauthenticated attacker on the same network can exploit this buffer overflow to cause a denial-of-service condition on the affected camera devices.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 modelLocate the device label or check the device management 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 model is one of the Binatoneglobal devices listed in the affected products list
-
Determine the installed firmware versionAccess the camera's settings page or administration interface and locate the firmware version information, typically found under 'Device Info', 'About', or 'Settings'Affected if The firmware version falls below the specified threshold for that model (Halo+ < 03.50.14, Comfort 85 Connect < 03.40.02, Mbp3855 < 03.40.00, Focus 72r < 03.40.00, or any version for Focus 68, Cn28, Cn50, Comfort 40)
-
Verify the local web server is enabledAttempt to access the camera's web interface by entering the camera's IP address in a web browser on the same network; confirm the HTTP service is respondingAffected if The web interface is accessible and responds to HTTP requests on the local network
-
Check network accessibility of the web serviceUse a network scanner or check firewall rules to determine if the camera's web server port (typically 80/443) is exposed beyond the local network segmentAffected if The web server is reachable from network segments other than the camera's local subnet, increasing exposure to unauthenticated attackers on the same network
The device is likely affected if it is a Binatone Hubble Camera model listed with an unpatched firmware version and its web server component is network-accessible.
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
Apply the vendor-supplied firmware update to the Hubble Cameras to patch the buffer overflow vulnerability. If no update is available, restrict network access to the camera's web interface by placing devices on an isolated network segment or VLAN.
Halo+ Camera: 03.50.14 | Comfort 85 Connect: 03.40.02 | Mbp3855: 03.40.00 | Focus 72r: 03.40.00 (Note: Focus 68, Cn28, Cn50, Comfort 40 have no fixed version listed - contact vendor)
- 1. Identify the specific camera model from the affected list (Halo+, Comfort 85 Connect, Mbp3855, Focus 68, Focus 72r, Cn28, Cn50, or Comfort 40)
- 2. Download the latest firmware for your device from binatoneglobal.com or the official Hubble camera support page
- 3. Access the camera's web interface on the local network
- 4. Navigate to the Settings or Administration section
- 5. Locate the Firmware Update or Upgrade option
- 6. Upload and apply the fixed firmware version (Halo+: 03.50.14+, Comfort 85 Connect: 03.40.02+, Mbp3855: 03.40.00+, Focus 72r: 03.40.00+)
- 7. Wait for the update to complete and verify the device reboots successfully
- 8. Confirm the firmware version has been updated to the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3790 — 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-3790 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