CVE-2019-9564
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 · uneditedA vulnerability in the authentication logic of Wyze Cam Pan v2, Cam v2, Cam v3 allows an attacker to bypass login and control the devices. This issue affects: Wyze Cam Pan v2 versions prior to 4.49.1.47. Wyze Cam v2 versions prior to 4.9.8.1002. Wyze Cam v3 versions prior to 4.36.8.32.
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 confidenceA critical authentication bypass vulnerability in Wyze Cam v2, v3, and Pan v2 devices allows unauthenticated attackers to gain full control of affected cameras by bypassing the login mechanism. The flaw exists in the authentication logic of specific firmware versions.
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.49.1.47< 4.9.8.1002< 4.36.8.32CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 Wyze camera modelCheck the physical device label or access Device Settings > Device Info in the Wyze mobile app to confirm whether the device is a Wyze Cam v2, Wyze Cam v3, or Wyze Cam Pan v2.Affected if The device is a Wyze Cam v2, v3, or Pan v2 model.
-
Locate the firmware versionIn the Wyze app, select the camera device, go to Device Settings, then Device Info, and record the Firmware Version number displayed.Affected if The firmware version cannot be retrieved from the device.
-
Compare Wyze Cam Pan v2 firmware versionIf the device is a Wyze Cam Pan v2, compare the installed firmware version (for example, 4.49.1.45) against the affected threshold of 4.49.1.47. Any version lower than 4.49.1.47 is affected.Affected if The device is a Wyze Cam Pan v2 with firmware version less than 4.49.1.47.
-
Compare Wyze Cam v2 firmware versionIf the device is a Wyze Cam v2, compare the installed firmware version (for example, 4.9.8.999) against the affected threshold of 4.9.8.1002. Any version lower than 4.9.8.1002 is affected.Affected if The device is a Wyze Cam v2 with firmware version less than 4.9.8.1002.
-
Compare Wyze Cam v3 firmware versionIf the device is a Wyze Cam v3, compare the installed firmware version (for example, 4.36.8.30) against the affected threshold of 4.36.8.32. Any version lower than 4.36.8.32 is affected.Affected if The device is a Wyze Cam v3 with firmware version less than 4.36.8.32.
A user is affected if they own a Wyze Cam v2, v3, or Pan v2 device running firmware version lower than the respective threshold (4.9.8.1002, 4.36.8.32, or 4.49.1.47), as these versions contain the authentication bypass vulnerability.
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.9.8.10024.36.8.324.49.1.47
Update Wyze Cam Pan v2 to version 4.49.1.47 or later, Wyze Cam v2 to version 4.9.8.1002 or later, and Wyze Cam v3 to version 4.36.8.32 or later to patch the authentication bypass.
Wyze Cam Pan V2: >= 4.49.1.47 | Wyze Cam V2: >= 4.9.8.1002 | Wyze Cam V3: >= 4.36.8.32
- Identify all Wyze Cam devices in your environment and note their specific models (Cam Pan V2, Cam V2, or Cam V3)
- Access each camera through the Wyze app and check the current firmware version under Device Settings > Device Info
- For Cam Pan V2 devices: Update firmware to version 4.49.1.47 or later via the Wyze app
- For Cam V2 devices: Update firmware to version 4.9.8.1002 or later via the Wyze app
- For Cam V3 devices: Update firmware to version 4.36.8.32 or later via the Wyze app
- Verify the firmware update was successful by rechecking the firmware version after update completes
- Restart each camera to ensure the new firmware is fully operational
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9564 — 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-2019-9564 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