dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-13892

HIGH · 7.7 CVSS v4.0 Published 2025-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/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
Smartwares cameras CIP-37210AT and C724IP, as well as others which share the same firmware in versions up to 3.3.0, are vulnerable to command injection. During the initialization process, a user has to use a mobile app to provide devices with Access Point credentials. This input is not properly sanitized, what allows for command injection. The vendor has not replied to reports, so the patching status remains unknown. Newer firmware versions might be vulnerable as well.

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 confidence

Smartwares IP cameras (CIP-37210AT, C724IP, and similar models) up to firmware 3.3.0 contain a command injection vulnerability in the Access Point credential setup process via the mobile app. User-supplied WiFi credentials are not sanitized before being passed to system shell commands, allowing arbitrary command execution on the device.

MitigationSince the vendor has not provided a patch, mitigations should focus on network isolation (VLAN segmentation, firewall rules restricting device communication) and monitoring for indicators of compromise. Consider replacing vulnerable devices with alternatives from vendors that provide timely security updates.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 your Smartwares camera model
    Locate the device label on the camera or check the web interface/device information page for the exact model number (e.g., CIP-37210AT, C724IP, or similar Smartwares IP camera models)
    Affected if The model is CIP-37210AT, C724IP, or another similar Smartwares IP camera model from the same product line
  2. Check the installed firmware version
    Access the camera's web interface (typically via IP address), navigate to Settings or System Information, and locate the firmware version field; alternatively, check via the mobile app device details
    Affected if The firmware version is 3.3.0 or lower (including unversioned firmware on older devices)
  3. Verify the Access Point setup feature is accessible
    Open the Smartwares mobile app (or web interface) and navigate to the Access Point / WiFi credential configuration section where wireless network names and passwords are entered for the camera's AP mode
    Affected if The Access Point credential configuration feature is present and functional on your device
  4. Confirm the device is network-adjacent to the vulnerability
    Determine if the camera is accessible on the network (via browser or mobile app) or if the mobile app can communicate with the camera for configuration
    Affected if The camera or its mobile app configuration interface is reachable from a network where an attacker could intercept or inject malicious WiFi credentials

You are affected if you have a Smartwares IP camera (CIP-37210AT, C724IP, or similar model) running firmware version 3.3.0 or lower, and the Access Point credential setup feature via the mobile app is accessible on your network.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the vendor has not provided a patch, mitigations should focus on network isolation (VLAN segmentation, firewall rules restricting device communication) and monitoring for indicators of compromise. Consider replacing vulnerable devices with alternatives from vendors that provide timely security updates.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-13892 — 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-13892 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