CVE-2024-6249
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 · uneditedWyze Cam v3 TCP Traffic Handling Stack-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 TUTK P2P library. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-22419.
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 confidenceStack-based buffer overflow in the TUTK P2P library of Wyze Cam v3 IP cameras allows remote, unauthenticated attackers to execute arbitrary code as root by sending specially crafted TCP traffic without validating data length before copying to a fixed-size stack buffer.
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< 4.36.11.8391CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLog into the Wyze app or web interface, or access the device directly via SSH if available, and retrieve the model information. Look for 'Wyze Cam v3' or 'WYZECV3' in the device specifications.Affected if The device is NOT a Wyze Cam v3 model - this vulnerability only affects that specific model.
-
Check the installed firmware versionIn the Wyze app, select the camera, tap the gear icon, then view 'Device Info' to find the firmware version. Alternatively, access the camera via SSH and run: cat /etc/version or cat /var/log/wyzecam_firmware.infoAffected if The firmware version is lower than 4.36.11.8391 - versions below this threshold contain the vulnerable code.
-
Verify TUTK P2P service exposureFrom a network-adjacent host, scan the camera's open ports using nmap -p 1-65535 <camera_ip> or check if port 8883 (default TUTK P2P port) is listening. The vulnerability is triggered by sending TCP packets to the P2P service.Affected if Port 8883 or other TUTK P2P ports are accessible from untrusted network segments - this indicates the attack surface is present.
-
Assess network accessibilityDetermine if the camera is reachable from network segments outside your trusted LAN/VLAN. Use ping <camera_ip> from untrusted networks or review firewall rules that may or may not permit traffic to the camera.Affected if The camera is directly accessible from untrusted networks without firewall filtering - exploitation requires no authentication and can be initiated by any network-adjacent attacker.
You are affected if you have a Wyze Cam v3 running firmware version 4.36.11.8391 or lower, and the TUTK P2P service (typically port 8883) is accessible from your network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped4.36.11.8391
Apply vendor firmware updates when available; until then, isolate affected devices on a restricted network segment and disable P2P/remote access features if possible to reduce attack surface.
Firmware version 4.36.11.8391 or later
- 1. Open the Wyze app on your mobile device
- 2. Select the affected Wyze Cam v3 camera
- 3. Navigate to the camera's settings menu
- 4. Check for firmware updates or manually verify current firmware version
- 5. If firmware version is below 4.36.11.8391, apply the available firmware update
- 6. After update completes, verify the camera is running firmware version 4.36.11.8391 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6249 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6249 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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