LiveActive security incident?Get immediate response
CVE Record

CVE-2023-34551: In certain EZVIZ products, two stack buffer overflows in netClientSetWlanCfg function of the EZVIZ SDK comm...

In certain EZVIZ products, two stack buffer overflows in netClientSetWlanCfg function of the EZVIZ SDK command server can allow an authenticated attacker present on the same local network as the camera to achieve remote code execution. This affects CS-C6N-B0-1G2WF Firmware versions before V5.3.0 build 230215 and CS-C6N-R101-1G2WF Firmware versions before V5.3.0 build 230215 and CS-CV310-A0-1B2WFR Firmware versions before V5.3.0 build 230221 and CS-CV310-A0-1C2WFR-C Firmware versions before V5.3.2 build 230221 and CS-C6N-A0-1C2WFR-MUL Firmware versions before V5.3.2 build 230218 and CS-CV310-A0-3C2WFRL-1080p Firmware versions before V5.2.7 build 230302 and CS-CV310-A0-1C2WFR Wifi IP66 2.8mm 1080p Firmware versions before V5.3.2 build 230214 and CS-CV248-A0-32WMFR Firmware versions before V5.2.3 build 230217 and EZVIZ LC1C Firmware versions before V5.3.4 build 230214. The impact is: execute arbitrary code (remote).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Certain EZVIZ camera firmware versions contain stack buffer overflow flaws that can let an authenticated attacker on the same local network run code on the camera. This is not described as internet-wide unauthenticated exploitation, but it matters for offices, sites, and homes with shared or weakly controlled local networks.

Executive priority

Treat as a high-priority firmware hygiene issue for exposed camera fleets. The business risk is local-network compromise of surveillance devices, not confirmed active exploitation from the provided sources.

Technical view

CVE-2023-34551 covers two stack buffer overflows in the EZVIZ SDK command server function netClientSetWlanCfg. The CVE states authenticated, same-LAN attackers may achieve remote arbitrary code execution on specified CS-C6N, CS-CV310, CS-CV248, and LC1C firmware versions before listed fixed builds.

Likely exposure

Exposure is likely limited to organizations or users running the listed EZVIZ camera models below the fixed firmware builds, especially where camera networks are reachable by many local users or devices.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The described attack requires authentication and presence on the same local network as the camera.

Researcher notes

Evidence is specific on vulnerable function, attack preconditions, impact, affected models, and fixed build cutoffs. The bundle lacks CVSS, CWE mapping, exploit maturity, proof-of-concept status, and detailed vendor remediation procedure beyond affected-version thresholds.

Mitigation direction

  • Identify all EZVIZ camera models and firmware versions in use.
  • Upgrade affected devices to the fixed builds listed by EZVIZ or later.
  • Review EZVIZ security notice and vendor firmware guidance before rollout.
  • Restrict camera network access to trusted administrative devices.
  • Segment camera networks from guest and general user networks.

Validation and detection

  • Compare device model numbers against the affected model list.
  • Compare installed firmware against the fixed build thresholds.
  • Confirm upgrades through the device interface or management inventory.
  • Check whether camera interfaces are reachable from untrusted local networks.
  • Review available device logs for unexpected authenticated access.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-34551 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.