Nest Hub Max: Improper Authentication
CVE-2023-2626 is a high-severity improper authentication vulnerability in Nest Hub Max from Google, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited from the same local network by an unauthenticated attacker, without any action from a user. The record lists version 10.20221207.2.120 as the first without the flaw, so updating Nest Hub Max to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.11% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Nest Hub Max to 10.20221207.2.120 or a later version.
- Update Nest Hub (2nd. gen) w/ Sleep Tracking to 10.20221207.2.100042 or a later version.
- Update Nest Wifi 6E to 1.63.355999 or a later version.
- Read the advisory on support.google.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Nest Hub Max | 10.20221207.2.109 up to, but not including, 10.20221207.2.120 | 10.20221207.2.120 | |
| Nest Hub (2nd. gen) w/ Sleep Tracking | 10.20221207.2.100038 up to, but not including, 10.20221207.2.100042 | 10.20221207.2.100042 | |
| Nest Wifi 6E | 1.59 up to, but not including, 1.63.355999 | 1.63.355999 | |
| Google Wifi (next gen) | 14150.881.7 up to, but not including, 14150.882.9 | 14150.882.9 | |
| Nest Wifi Point | 1.56.1 up to, but not including, 1.56.368671 | 1.56.368671 | |
| nest_hub | 10.20221207.2.100038 up to, but not including, 10.20221207.2.100042 | 10.20221207.2.100042 | |
| wifi | 14150.881.7 up to, but not including, 14150.882.9 | 14150.882.9 | |
| Nest Hub Max Firmware | 10.20221207.2.109 up to, but not including, 10.20221207.2.120 | 10.20221207.2.120 | |
| Nest Hub Firmware | 10.20221207.2.100038 up to, but not including, 10.20221207.2.100042 | 10.20221207.2.100042 | |
| WiFi Firmware | 14150.881.7 up to, but not including, 14150.882.9 | 14150.882.9 | |
| Nest WiFi Point Firmware | 1.56.1 up to, but not including, 1.56.368671 | 1.56.368671 | |
| Nest WiFi 6e Firmware | 1.59 up to, but not including, 1.63.355999 | 1.63.355999 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- AdjacentThe attacker must be on the same local network segment.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (google.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
There exists an authentication bypass vulnerability in OpenThread border router devices and implementations. This issue allows unauthenticated nodes to craft radio frames using “Key ID Mode 2”: a special mode using a static encryption key to bypass security checks, resulting in arbitrary IP packets being allowed on the Thread network. This provides a pathway for an attacker to send/receive arbitrary IPv6 packets to devices on the LAN, potentially exploiting them if they lack additional authentication or contain any network vulnerabilities that would normally be mitigated by the home router’s NAT firewall. Effected devices have been mitigated through an automatic update beyond the affected range.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Improper Authentication vulnerabilities
- 9.8 Critical severity
- 7.5 High severity
- 9.8 Critical severity
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
Spotted an error? Tell us.