CVE-2021-3789: An information disclosure vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker with phys
Noroxi assessment
Priority: Monitor (action score 18/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An information disclosure vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker with physical access to obtain the encryption key used to decrypt firmware update packages.
- Published
- Nov 12, 2021
- Updated
- Jun 17, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-522
Report tools
Action score
18
Monitor
Low priority for now.
- CVSS
- 18 / 40 · 4.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
CNA vs NVD score
- NVD
- 4.6
- CNA · lenovo
- 4.2
- 0.4 point gap
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| binatoneglobal | halo\+ camera firmware | cpe:2.3:o:binatoneglobal:halo\+_camera_firmware |
| binatoneglobal | halo\+ camera | cpe:2.3:h:binatoneglobal:halo\+_camera |
| binatoneglobal | comfort 85 connect firmware | cpe:2.3:o:binatoneglobal:comfort_85_connect_firmware |
| binatoneglobal | comfort 85 connect | cpe:2.3:h:binatoneglobal:comfort_85_connect |
| binatoneglobal | mbp3855 firmware | cpe:2.3:o:binatoneglobal:mbp3855_firmware |
| binatoneglobal | mbp3855 | cpe:2.3:h:binatoneglobal:mbp3855 |
| binatoneglobal | focus 68 firmware | cpe:2.3:o:binatoneglobal:focus_68_firmware |
| binatoneglobal | focus 68 | cpe:2.3:h:binatoneglobal:focus_68 |
| binatoneglobal | focus 72r firmware | cpe:2.3:o:binatoneglobal:focus_72r_firmware |
| binatoneglobal | focus 72r | cpe:2.3:h:binatoneglobal:focus_72r |
| binatoneglobal | cn28 firmware | cpe:2.3:o:binatoneglobal:cn28_firmware |
| binatoneglobal | cn28 | cpe:2.3:h:binatoneglobal:cn28 |
and 30 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- binatoneglobal cn28 firmwareall versions
- binatoneglobal cn40 firmwareall versions
- binatoneglobal cn50 firmwareall versions
- binatoneglobal cn75 firmwareall versions
- binatoneglobal comfort 40 firmwareall versions
- binatoneglobal comfort 50 connect firmwareall versions
- binatoneglobal comfort 85 connect firmwarebefore 03.40.02
- binatoneglobal connect 20 firmwareall versions
- binatoneglobal connect view 65 firmwareall versions
- binatoneglobal ease44 firmwareall versions
- binatoneglobal focus 68 firmwareall versions
- binatoneglobal focus 72r firmwarebefore 03.40.00
- binatoneglobal halo+ camera firmwarebefore 03.50.14
- binatoneglobal lux 64 firmwareall versions
- binatoneglobal lux 65 firmwareall versions
- binatoneglobal lux 85 connect firmwareall versions
- binatoneglobal mbp3667 firmwareall versions
- binatoneglobal mbp3855 firmwarebefore 03.40.00
- binatoneglobal mbp4855 firmwareall versions
- binatoneglobal mbp669 connect firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (lenovo). Independent of NVD's CPE analysis and usually ahead of it.
Motorola Binatone Hubble Cameras
- variousaffected
Same product
binatoneglobal: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3577An unauthenticated remote code execution vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an att53Plan
- CVE-2021-3787A vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker with local access to obtain the M31Monitor
- CVE-2021-3788An exposed debug interface was reported in some Motorola-branded Binatone Hubble Cameras that could allow an attacker with physical access u27Monitor
Published before and after this one in the same product
- Later →CVE-2021-3790Nov 12, 2021 · A buffer overflow was reported in the local web server of some Motorola-branded Binatone Hubble Cameras that could allow an unauthenticated 26Monitor
- Later →CVE-2021-3791Nov 12, 2021 · An information disclosure vulnerability was reported in some Motorola-branded Binatone Hubble Cameras that could allow an unauthenticated at26Monitor
- Later →CVE-2021-3792Nov 12, 2021 · Some device communications in some Motorola-branded Binatone Hubble Cameras with backend Hubble services are not encrypted which could lead 21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-522 · Insufficiently Protected CredentialsCVSS vector
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Session SidejackingCAPEC-102likelihood: High · High
- Signature Spoofing by Key TheftCAPEC-474likelihood: Medium · High
- Password Recovery ExploitationCAPEC-50likelihood: Medium · High
- KerberoastingCAPEC-509High
- Modify Existing ServiceCAPEC-551
- Remote Services with Stolen CredentialsCAPEC-555Very High
- Use of Known Domain CredentialsCAPEC-560likelihood: High · High
- Windows Admin Shares with Stolen CredentialsCAPEC-561
ATT&CK techniques
- Remote ServicesT1021
- Remote Services:SMB/Windows Admin SharesT1021.002
- Valid AccountsT1078
- Brute Force:Credential StuffingT1110.004
- Email Collection:Remote Email CollectionT1114.002
- External Remote ServicesT1133
- Create or Modify System ProcessT1543
- Use Alternate Authentication Material:Pass The HashT1550.002
- Use Alternate Authentication Material:Pass The TicketT1550.003
- Unsecured Credentials: Private KeysT1552.004
- Steal or Forge Kerberos TicketsT1558
- Steal or Forge Kerberos Tickets:KerberoastingT1558.003
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.