CVE-2024-6247
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 Wi-Fi SSID OS Command Injection Remote Code Execution Vulnerability. This vulnerability allows physically present 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 handling of SSIDs embedded in scanned QR codes. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-22337.
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 confidenceOS command injection vulnerability in Wyze Cam v3 IP cameras. The device fails to validate SSID strings from QR codes before passing them to a system call, allowing injected shell commands to execute with root privileges. Physically present attackers can scan a malicious QR code to achieve unauthenticated RCE.
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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:P/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.
-
Locate Wyze Cam v3 firmware versionOpen the Wyze app, select your Wyze Cam v3 device, tap the gear icon, and scroll to Device Info to find the Firmware version fieldAffected if Firmware version is displayed as a version number that can be compared
-
Compare firmware version against affected rangeIf the firmware version shown is below 4.36.11.8391, the device is running a vulnerable version; versions are typically formatted as X.YY.Z.ZZZZAffected if Firmware version begins with a number lower than 4.36, or equals 4.36 but the full version number is below .8391 (for example, 4.36.10.1234)
-
Check for firmware update availabilityIn the Wyze app device settings, look for the Firmware Update option or check if an update badge appears on the device cardAffected if An update is available, suggesting the current version is outdated and likely affected
The device is affected if the Wyze Cam v3 firmware version is less than 4.36.11.8391, which can be confirmed through the Wyze app device information screen.
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, restrict physical access to devices and segment camera networks to limit exposure.
Wyze Cam v3 Firmware 4.36.11.8391 or later
- 1. Access the Wyze app on a mobile device connected to your account
- 2. Navigate to the Wyze Cam v3 device settings
- 3. Check the current firmware version under Device Info or Settings > Device Info
- 4. If firmware version is below 4.36.11.8391, initiate a firmware update through the app
- 5. Ensure the camera remains powered on and connected to the internet during the update process
- 6. After update completes, verify the firmware version has changed to 4.36.11.8391 or later
- 7. As a further security measure, ensure the camera is placed in a physically secure location to prevent unauthorized physical access
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6247 — 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-6247 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