CVE-2024-48214
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 · uneditedKERUI HD 3MP 1080P Tuya Camera 1.0.4 has a command injection vulnerability in the module that connects to the local network via a QR code. This vulnerability allows an attacker to create a custom, unauthenticated QR code and abuse one of the parameters, either SSID or PASSWORD, in the JSON data contained within the QR code. By that, the attacker can execute arbitrary code on the camera.
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 · moderate confidenceKERUI HD 3MP 1080P Tuya Camera firmware 1.0.4 contains a command injection vulnerability in the QR code network configuration module. An unauthenticated attacker can craft a malicious QR code containing shell commands in either the SSID or PASSWORD JSON fields, which the camera processes without proper input sanitization, leading to arbitrary code execution on the device.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 device modelCheck the device label, packaging, or administrative interface for the exact model name (KERUI HD 3MP 1080P Tuya Camera)Affected if Device is not the KERUI HD 3MP 1080P Tuya Camera, then not affected by this specific CVE
-
Check firmware versionAccess the camera admin panel or check via ONVIF/Tuya app to locate the firmware version informationAffected if Firmware version is 1.0.4 exactly, indicating it matches the affected version
-
Locate firmware version via web interface or APINavigate to the camera settings page (usually /config or /deviceinfo) or use the Tuya mobile app device details to view the installed firmware buildAffected if Firmware version cannot be determined or differs from 1.0.4, still compare against the affected range
-
Verify QR code network setup feature presenceCheck camera settings or mobile app for QR code or network setup by scanning optionsAffected if QR code network setup feature is present and accessible on the device
-
Confirm QR code processing for SSID/PASSWORDReview camera network configuration options to confirm the device accepts QR codes containing JSON with SSID and PASSWORD fields for WiFi setupAffected if The device processes QR codes containing SSID/PASSWORD parameters for network configuration
The device is affected if it is a KERUI HD 3MP 1080P Tuya Camera running firmware 1.0.4 with the QR code network setup feature enabled and capable of processing QR codes with SSID/PASSWORD parameters.
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.
From vendor dataUsers should refrain from scanning untrusted QR codes with the camera until a vendor firmware patch is released. The vendor must implement proper input validation and sanitization on the SSID and PASSWORD parameters before passing them to any system call or shell execution function.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-48214 — 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-48214 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