Cam v2: Improper Neutralization of Special Elements used in a Command
CVE-2023-6321 is a high-severity improper neutralization of special elements used in a command vulnerability in Cam v2 from Owlet, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 4.2.10 as the first without the flaw, so updating Cam v2 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 2.75% chance of exploitation within 30 days, higher than 86% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Cam v2 to 4.2.10 or a later version.
- Update Cam v1 to 4.2.11 or a later version.
- Update Cam Firmware to 4.2.11 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Owlet | Cam v2 | before 4.2.10 | 4.2.10 |
| Owlet | Cam v1 | before 4.2.11 | 4.2.11 |
| Owletcare | Cam Firmware | before 4.2.11 | 4.2.11 |
| Owletcare | Cam 2 Firmware | before 4.2.10 | 4.2.10 |
| Throughtek | Kalay Platform | Not specified in the record | Not stated |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- 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:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | CNA (bitdefender.com) |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
A command injection vulnerability exists in the IOCTL that manages OTA updates. A specially crafted command can lead to command execution as the root user. An attacker can make authenticated requests to trigger this vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in a Command
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
How developers prevent this class of flaw
- If at all possible, use library calls rather than external processes to recreate the desired functionality.
- If possible, ensure that all external commands called from the program are statically created.
- Run time: Run time policy enforcement may be used in an allowlist fashion to prevent use of any non-sanctioned commands.
More Improper Neutralization of Special Elements used in a Command vulnerabilities (CWE-77)
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
Technical write-ups (may include proof of concept)
- bitdefender.com/blog/labs/notes-on-throughtek-kalay-vulnerabilities-and-their-impact/Exploit, Third Party Advisory
Recent Improper Neutralization of Special Elements used in a Command vulnerabilities
- 9.8 Critical severity
- 8.0 High severity
- 9.8 Critical severity
- 7.2 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.