dbcve.org
Cam V3 FirmwareOperating system · Wyze

CVE-2024-6248

HIGH · 7.5 CVSS v3.0 Published 2024-11-22
Fix available
A fix is available. Upgrade to 4.36.11.8391 or later.
See remediation →
80/100
Remediation priority · High
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 Cloud Infrastructure Improper Authentication 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 run_action_batch endpoint of the cloud infrastructure. The issue results from the use of the device's MAC address as a sole credential for authentication. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of root. Was ZDI-CAN-22393.

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

The vulnerability exists in the Wyze Cam v3 cloud infrastructure's run_action_batch endpoint, which uses only the device's MAC address as authentication. Since MAC addresses can be easily discovered or spoofed, unauthenticated network-adjacent attackers can send requests to execute arbitrary code in the context of root.

MitigationOrganizations should implement network segmentation to isolate IoT/camera devices, monitor for unauthorized device communications, and apply vendor patches when Wyze releases firmware updates addressing this cloud infrastructure flaw.

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

CVSS:3.0/AV:A/AC:H/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 Wyze Cam v3 devices in your environment
    Locate all Wyze Cam v3 cameras on your network by checking device DHCP leases, MAC address OUI (24:4B:FE or 3C:8D:20 prefixes), or physical inspection of device labels
    Affected if Wyze Cam v3 devices are present on the network
  2. Check installed firmware version
    Access the Wyze app or camera web interface and navigate to Device Settings > About > Firmware Version, or query the camera's local API at http://[camera_ip]/api/info
    Affected if Firmware version is lower than 4.36.11.8391 (for example, 4.36.10.x or earlier)
  3. Verify cloud connectivity exists
    Check if the camera maintains outbound connections to Wyze cloud servers (typically wyze.com, api.wyze.com, or similar domains on ports 443/80) via network traffic monitoring or firewall logs
    Affected if Camera can reach Wyze cloud infrastructure without network segmentation blocks
  4. Assess network segmentation status
    Review network firewall rules, VLAN assignments, or access control lists to determine if camera devices are isolated from untrusted network segments or the internet
    Affected if Camera is on the same network segment as untrusted devices and can communicate directly with Wyze cloud without restriction

You are affected if you have Wyze Cam v3 devices running firmware versions below 4.36.11.8391 that can communicate with Wyze cloud services without network isolation.

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

Organizations should implement network segmentation to isolate IoT/camera devices, monitor for unauthorized device communications, and apply vendor patches when Wyze releases firmware updates addressing this cloud infrastructure flaw.

Recommended fix High confidence

4.36.11.8391

  1. Check current firmware version on the Wyze Cam v3 device through the Wyze app or web interface
  2. Navigate to device settings and check for available firmware updates
  3. Update the camera firmware to version 4.36.11.8391 or later through the Wyze app or official Wyze support channels
  4. Verify the firmware has been successfully updated by checking the device information after the update completes
  5. Ensure the camera reconnects to the network and functions normally

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

Fix this in Cam V3 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 the upgrade done

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-2024-6248 — 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-6248 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