dbcve.org
Cam V3 FirmwareOperating system · Wyze

CVE-2024-6246

HIGH · 8.8 CVSS v3.1 Published 2024-11-22
Fix available
A fix is available. Upgrade to 4.36.11.8391 or later.
See remediation →
93/100
Remediation priority · Urgent
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
Wyze Cam v3 Realtek Wi-Fi Driver Heap-Based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Wyze Cam v3 IP cameras. Authentication is not required to exploit this vulnerability. The specific flaw exists within the Realtek Wi-Fi kernel module. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a heap-based buffer. An attacker can leverage this vulnerability to execute code in the context of the kernel. Was ZDI-CAN-22310.

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

Heap-based buffer overflow vulnerability in the Realtek Wi-Fi kernel module of Wyze Cam v3 IP cameras. The flaw results from insufficient validation of user-supplied data length before copying to a heap-allocated buffer, enabling network-adjacent attackers to execute arbitrary code in kernel context without authentication.

MitigationApply vendor firmware update when available; until then, isolate affected devices on restricted network segments and minimize exposure to untrusted networks.

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
Cam V3 FirmwareOperating system
Affected:< 4.36.11.8391

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

CVSS:3.1/AV:A/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. Check Wyze Cam v3 firmware version
    Access the Wyze mobile app, select the Wyze Cam v3 device, and navigate to Device Settings > Device Info to view the firmware version. Alternatively, check the camera's web interface if accessible.
    Affected if The firmware version is lower than 4.36.11.8391
  2. Confirm device is Wyze Cam v3
    Verify the exact model number of the camera. The vulnerability specifically affects Wyze Cam v3 (not v1 or v2). Check the device label or app device info for model identification.
    Affected if The device model is Wyze Cam v3 and firmware is below 4.36.11.8391
  3. Verify Wi-Fi is enabled
    Check if the camera is connected via Wi-Fi. In the Wyze app, verify the camera's connection status shows a Wi-Fi network (not ethernet). The vulnerability exists in the Realtek Wi-Fi kernel module.
    Affected if Wi-Fi is enabled and the firmware version is below 4.36.11.8391
  4. Assess network accessibility
    Determine if the camera is on a network accessible to untrusted actors. The flaw requires network-adjacent attacker proximity. Check if the camera is on the same network segment as untrusted devices or directly exposed to the internet.
    Affected if The camera is on a network where untrusted, network-adjacent attackers can reach it and firmware is vulnerable

The environment is affected if a Wyze Cam v3 device is running firmware version below 4.36.11.8391, has Wi-Fi enabled, and is accessible to network-adjacent attackers.

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
Upgrade available Upgrade to 4.36.11.8391 or later
Fixed in 4.36.11.8391
Interim mitigation

Apply vendor firmware update when available; until then, isolate affected devices on restricted network segments and minimize exposure to untrusted networks.

Recommended fix High confidence

Wyze Cam V3 Firmware 4.36.11.8391 or later

  1. Locate the Wyze Cam v3 device in the Wyze app
  2. Navigate to the device settings for the affected camera
  3. Check the current firmware version under Device Info or About
  4. If firmware version is below 4.36.11.8391, initiate firmware update through the Wyze app
  5. Ensure stable power connection during the firmware update process
  6. Allow update to complete fully without interrupting power
  7. Verify the updated firmware version shows 4.36.11.8391 or later after completion
Caveat Standard firmware update precautions apply - ensure uninterrupted power and stable network during upgrade

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

Fix this in Cam V3 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6246 — 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-2024-6246 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