Cs C6n A0 1c2wfr FirmwareOperating system · Ezviz

CVE-2022-2472

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
Improper Initialization vulnerability in the local server component of EZVIZ CS-C6N-A0-1C2WFR allows a local attacker to read the contents of the memory space containing the encrypted admin password. This issue affects: EZVIZ CS-C6N-A0-1C2WFR versions prior to 5.3.0 build 220428.

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

Improper initialization in the local server component of EZVIZ CS-C6N-A0-1C2WFR camera firmware allows a local attacker to read uninitialized memory containing the encrypted admin password. This occurs because memory is not properly initialized before use, leaking sensitive credential data to a local attacker.

MitigationUpgrade EZVIZ CS-C6N-A0-1C2WFR firmware to version 5.3.0 build 220428 or later. As a local attack vector, restrict physical and local network access to the device.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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 device model
    Locate the model number on the device label or in the device management interface. Confirm it is EZVIZ CS-C6N-A0-1C2WFR.
    Affected if Device model is EZVIZ CS-C6N-A0-1C2WFR and firmware version is 5.3.0 exactly.
  2. Check firmware version
    Access the camera through its web interface or mobile app and navigate to the device settings or system information section to view the installed firmware version.
    Affected if Firmware version displayed is exactly 5.3.0.
  3. Verify local server accessibility
    Attempt to access the local server component on the device from the local network using the device IP address on common ports (such as 80, 443, 8000, or vendor-specific ports).
    Affected if Local server is accessible from the local network on a device running firmware 5.3.0.
  4. Confirm vulnerability scope
    This vulnerability allows reading uninitialized memory through the local server component. The flaw exists in firmware version 5.3.0; later builds (such as 220428 or newer) contain the fix.
    Affected if Device runs firmware 5.3.0 build earlier than 220428.

You are affected if you have an EZVIZ CS-C6N-A0-1C2WFR camera running firmware version 5.3.0 with local server accessibility.

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

Upgrade EZVIZ CS-C6N-A0-1C2WFR firmware to version 5.3.0 build 220428 or later. As a local attack vector, restrict physical and local network access to the device.

Recommended fix Moderate confidence

EZVIZ CS-C6N-A0-1C2WFR firmware 5.3.0 build 220428 or later

  1. 1. Download the latest firmware version 5.3.0 build 220428 or later from the official EZVIZ support website
  2. 2. Access the camera's web interface or EZVIZ mobile application
  3. 3. Navigate to the device settings or firmware upgrade section
  4. 4. Upload the downloaded firmware file and initiate the upgrade process
  5. 5. Wait for the upgrade to complete and the device to restart
  6. 6. Verify the firmware version has been updated successfully
Caveat Ensure stable power during firmware upgrade to avoid device bricking; backup any custom configurations before upgrading

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2472 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