Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network position (same LAN/Wi-Fi)
-
DeliveryPerform man-in-the-middle / spoof TLS endpoint
-
ExploitCamera accepts invalid certificate (CWE-295)
-
ExecutionIntercept or alter camera communications
-
ImpactDisclose video/credential data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V12 - Secure Communication Certificate validation
|
| Exploitation Conditions | Exploitation requires the attacker to be network-adjacent to the camera - on the same local/Wi-Fi segment - and to establish a man-in-the-middle position (the AT:P attack requirement); the device then fails to validate the TLS server certificate (CWE-295), allowing interception. Passive user interaction (UI:P) is also needed, meaning the victim's normal camera/app activity must occur for traffic to be captured. Key LIMITING factors: no remote/internet-based exploitation (AV:A, not AV:N), dependency on first obtaining the adjacent MITM position, and the products being sold exclusively in the Chinese market, which sharply narrows the realistic target population. |
| Impact | This is a medium-severity (CVSS 4.0 base 5.9) improper certificate validation flaw (CWE-295) in Lenovo consumer smart cameras, and the signal picture is internally consistent and points to a LOW real-world priority rather than an urgent one. The CVSS 4.0 vector (AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N) confirms the attacker must be network-adjacent (same L2/Wi-Fi segment), needs a specific attack requirement to be met (AT:P - i.e. a man-in-the-middle position), requires passive user interaction, and gains only confidentiality impact. No EPSS score was supplied in the input, there is no CISA KEV listing, and no public POC was referenced, so exploitation status is 'no public exploit identified at time of analysis.' The one notable tension is between the vector and the description: the vendor scored VI:N (no integrity impact), yet the description explicitly states communications could be 'intercept[ed] or manipulat[ed]' - manipulation implies an integrity impact that the published vector does not reflect; verify the integrity scoring with Lenovo. Combined with the adjacent-only vector and MITM prerequisite, this is a genuine-but-contained privacy risk, not a widely-automatable mass-exploitation threat. |
| Exploit ScenarioDerived | An attacker who has already gained a position on the same local or Wi-Fi network as the camera (e.g. a shared/compromised home or small-office WLAN) performs a man-in-the-middle attack and, because the device fails to properly validate TLS certificates, transparently intercepts the camera's traffic to capture video/credentials or alter the data in transit. No public exploit code was referenced, and the attack depends on achieving the adjacent MITM position plus the victim's normal device activity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Improper TLS certificate validation in Lenovo Smart Camera firmware lets a network-adjacent attacker who has already established a man-in-the-middle position on the same local or Wi-Fi segment intercept the camera's network communications and read the traffic it protects. Unauthenticated attackers are sufficient (PR:N), and only the victim's ordinary camera or companion-app activity is required for capture (passive user interaction), with high confidentiality impact but no availability impact. Affected devices include the Smart Camera C33, C33 Pro, C35, RQ3, XW1, X6T, X6Q, C5X and X9T plus the Smart Network PTZ X5T, X5Q and X5E, all sold exclusively in the Chinese market, which sharply narrows the realistic target population. No public exploit identified at time of analysis and no CISA KEV listing; at CVSS 4.0 base 5.9 this is a medium-severity, low real-world priority issue rather than an urgent one, consistent with the requirement to first obtain an adjacent MITM position and with the absence of internet-facing exposure.
RemediationAI
No vendor-released fixed firmware version is specified in the available intelligence - the advisory at https://iknow.lenovo.com.cn/detail/442625 (Lenovo China, IKnow) is the authoritative source and should be consulted directly for a per-model firmware update or a statement that the affected models have been discontinued; register affected devices in Lenovo's support channels and apply any firmware issued for the C33/C33 Pro, C35, RQ3, XW1, X6T/X6Q, C5X, X9T and the X5T/X5Q/X5E PTZ line, and treat the flaw as resolved only by a firmware release that restores proper certificate chain and hostname validation. Until vendor firmware is confirmed available, the most effective compensating control is to remove the opportunity for an adjacent man-in-the-middle: place the cameras on a dedicated WLAN/VLAN with client isolation and WPA3, and never attach them to shared, public, guest or untrusted Wi-Fi; the trade-off is that camera-to-phone/cloud discovery within the home network may need explicit firewall allowances. Encapsulate camera traffic so that a spoofed local certificate cannot succeed - a TLS-terminating VPN or a trusted router product with strict certificate pinning and DNS validation - at the cost of added latency and client configuration on mobile devices. Hardening the local segment (dynamic ARP inspection, DHCP snooping, port security, rogue-AP and DNS-spoofing monitoring, disabling unused LAN-facing services such as RTSP/ONVIF where not needed) also suppresses the MITM prerequisite, though these controls require managed switching equipment most consumer homes lack. Because the flaw is confined to confidentiality of local traffic with no availability impact, sensitive viewing (e.g. live monitoring of premises) should be confined to trusted networks until a patched firmware is confirmed; note that none of these measures is equivalent to the vendor fix, since the underlying improper certificate validation remains present on the device.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 12 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause class is CWE-295, Improper Certificate Validation: the camera's firmware (or its TLS client stack when connecting to cloud or companion services) does not correctly verify the server certificate chain, hostname and trust anchor, so a forged or substituted certificate is accepted. In practice this defeats the confidentiality guarantees of TLS on the local segment: an attacker who can position themselves between the camera and its peer - via ARP cache poisoning, a rogue access point, DNS or gateway spoofing - can present an arbitrary certificate and terminate the TLS session transparently. The CVSS 4.0 vector (AV:A/AC:L/AT:P/PR:N/UI:P) confirms the prerequisites: adjacent network access, no authentication required, Attack Requirements Present (the MITM position must be established) and passive user interaction. The vector credits high confidentiality impact (VC:H) while scoring integrity and availability as none (VI:N/VA:N); our independent CVSS 3.1 assessment (AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N) rates integrity impact as high as well, reflecting the advisory's statement that communications could be manipulated, not merely read. The affected CPEs use wildcarded versions (lenovo:smart_camera_c33, smart_camera_c33_pro, smart_camera_c35, smart_camera_rq3, smart_camera_xw1, smart_camera_x6t, smart_camera_x6q, smart_network_ptz_x5t, smart_network_ptz_x5q, smart_network_ptz_x5e), indicating an unbounded firmware version range rather than a single confirmed bad build, and the additional tagged models (C5X, X9T) suggest the flaw is common code shared across the family rather than model-specific.
Know when Smart Camera C33 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Adjacent MITM needs a privileged network position (AV:A, AC:H) and victim activity (UI:R); failed cert validation permits both interception (C:H) and manipulation (I:H) with no availability impact.
Primary rating from Vendor (lenovo).
CVSS VectorVendor: lenovo
Lifecycle Timeline
1DescriptionCVE.org
A potential improper certificate validation vulnerability was reported in Lenovo Smart Camera C33, distributed exclusively in the Chinese market, that could allow an adjacent user to intercept or manipulate network communications.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-102532
GHSA-3hh9-228g-qmjp
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB