dbcve.org
Cs C6n A0 1c2wfr FirmwareOperating system · Ezviz

CVE-2022-2471

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Stack-based Buffer Overflow vulnerability in the EZVIZ Motion Detection component as used in camera models CS-CV248, CS-C6N-A0-1C2WFR, CS-DB1C-A0-1E2W2FR, CS-C6N-B0-1G2WF, CS-C3W-A0-3H4WFRL allows a remote attacker to execute remote code on the device. This issue affects: EZVIZ CS-CV248 versions prior to 5.2.3 build 220725. EZVIZ CS-C6N-A0-1C2WFR versions prior to 5.3.0 build 220428. EZVIZ CS-DB1C-A0-1E2W2FR versions prior to 5.3.0 build 220802. EZVIZ CS-C6N-B0-1G2WF versions prior to 5.3.0 build 220712. EZVIZ CS-C3W-A0-3H4WFRL versions prior to 5.3.5 build 220723.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in the EZVIZ motion detection component allows remote attackers to overflow a stack-allocated buffer by providing specially crafted motion detection data, enabling arbitrary code execution on affected camera models.

MitigationUpdate affected camera firmware to the specified patched versions: CS-CV248 to 5.2.3 build 220725, CS-C6N-A0-1C2WFR to 5.3.0 build 220428, CS-DB1C-A0-1E2W2FR to 5.3.0 build 220802, CS-C6N-B0-1G2WF to 5.3.0 build 220712, and CS-C3W-A0-3H4WFRL to 5.3.5 build 220723.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Cs C6n A0 1c2wfr FirmwareOperating system
Affected:= 5.3.0
Cs Db1c A0 1e2w2fr FirmwareOperating system
Affected:= 5.3.0
Cs C6n B0 1g2wf FirmwareOperating system
Affected:= 5.3.0
Cs C3w A0 3h4wfrl FirmwareOperating system
Affected:= 5.3.5
Cs Cv248 FirmwareOperating system
Affected:= 5.2.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the EZVIZ camera model
    Locate the model number on the camera physical label, or check via the EZVIZ mobile app under Device Settings, or access the camera web interface and look for the model identifier (Cs C6n, Cs Db1c, Cs C3w, or Cs Cv248)
    Affected if The camera model is one of: Cs C6n A0 1c2wfr, Cs Db1c A0 1e2w2fr, Cs C6n B0 1g2wf, Cs C3w A0 3h4wfrl, or Cs Cv248
  2. Check the installed firmware version
    In the EZVIZ app, go to Device Settings > Device Info > Firmware Version; or log into the camera web interface and check the version information page; note the exact firmware build number
    Affected if The firmware version matches 5.3.0 (for C6n A0, Db1c A0, C6n B0), 5.3.5 (for C3w A0), or 5.2.1 (for Cv248)
  3. Verify motion detection feature is enabled
    In the EZVIZ app, go to Device Settings > Detection Settings > Motion Detection and confirm the feature toggle is turned on; or check via the camera web interface under motion detection settings
    Affected if Motion detection is enabled and the camera is actively processing motion detection data

A user is affected if they own one of the listed EZVIZ camera models (C6n A0, Db1c A0, C6n B0, C3w A0, or Cv248) running the specific vulnerable firmware version (5.3.0, 5.3.5, or 5.2.1) with motion detection feature enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected camera firmware to the specified patched versions: CS-CV248 to 5.2.3 build 220725, CS-C6N-A0-1C2WFR to 5.3.0 build 220428, CS-DB1C-A0-1E2W2FR to 5.3.0 build 220802, CS-C6N-B0-1G2WF to 5.3.0 build 220712, and CS-C3W-A0-3H4WFRL to 5.3.5 build 220723.

Recommended fix High confidence

EZVIZ firmware 5.2.3 build 220725 (CS-CV248), 5.3.0 build 220428 (CS-C6N-A0-1C2WFR), 5.3.0 build 220802 (CS-DB1C-A0-1E2W2FR), 5.3.0 build 220712 (CS-C6N-B0-1G2WF), or 5.3.5 build 220723 (CS-C3W-A0-3H4WFRL) depending on model

  1. Identify the exact camera model from: CS-CV248, CS-C6N-A0-1C2WFR, CS-DB1C-A0-1E2W2FR, CS-C6N-B0-1G2WF, or CS-C3W-A0-3H4WFRL
  2. Access the EZVIZ device settings interface or EZVIZ mobile application
  3. Navigate to the firmware or device settings section
  4. Check the current firmware version and build number
  5. Download the appropriate fixed firmware from EZVIZ's official support website based on your model
  6. For CS-CV248: Upgrade to firmware version 5.2.3 build 220725 or later
  7. For CS-C6N-A0-1C2WFR: Upgrade to firmware version 5.3.0 build 220428 or later
  8. For CS-DB1C-A0-1E2W2FR: Upgrade to firmware version 5.3.0 build 220802 or later
Caveat Ensure stable power during firmware update to avoid device bricking; review EZVIZ release notes for any feature changes in newer firmware versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cs C6n A0 1c2wfr Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2471 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2471 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data