dbcve.org
Iota All In One Security Kit FirmwareOperating system · Goabode

CVE-2022-33195

CRITICAL · 10.0 CVSS v3.1 Published 2022-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable 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
Four OS command injection vulnerabilities exist in the XCMD testWifiAP functionality of Abode Systems, Inc. iota All-In-One Security Kit 6.9X and 6.9Z. A XCMD can lead to arbitrary command execution. An attacker can send a sequence of malicious commands to trigger these vulnerabilities.This vulnerability focuses on the unsafe use of the `WL_DefaultKeyID` in the function located at offset `0x1c7d28` of firmware 6.9Z, and even more specifically on the command execution occuring at offset `0x1c7fac`.

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 confidence

OS command injection vulnerability in Abode Systems iota All-In-One Security Kit firmware versions 6.9X and 6.9Z. The XCMD testWifiAP functionality uses the WL_DefaultKeyID parameter unsafely at memory offset 0x1c7d28, allowing arbitrary command execution at offset 0x1c7fac when malicious input is passed.

MitigationVendor-supplied firmware patch to implement proper input validation and use safe command execution methods (e.g., avoiding shell invocation with user-controlled parameters). Until patch is available, network segmentation and restricting device management access to trusted users is recommended.

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
Iota All In One Security Kit FirmwareOperating system
Affected:= 6.9x= 6.9z

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device's web interface or mobile app and locate the device information or status page to confirm it is an Abode iota All-In-One Security Kit.
    Affected if The device is not an Abode iota All-In-One Security Kit, as this vulnerability only affects that specific product line.
  2. Check the installed firmware version
    Navigate to the device settings or system information page in the web interface or mobile app, or query the device status API for the firmware version string.
    Affected if The firmware version begins with 6.9x or 6.9z (e.g., 6.9X, 6.9Z, 6.9.0, 6.9.1) indicating it matches the affected version ranges.
  3. Confirm XCMD functionality is accessible
    Attempt to access or query the XCMD endpoint on the device (typically exposed via the local API or debug interface). Check if testWifiAP command is available by reviewing API documentation or probing the endpoint with an authenticated request.
    Affected if The XCMD testWifiAP command is exposed and accepts parameters, enabling the vulnerable code path to be reached.
  4. Verify WL_DefaultKeyID parameter handling
    If XCMD access is available, examine how the WL_DefaultKeyID parameter is processed when calling testWifiAP. Inspect whether the parameter is passed directly to a shell command or system call without sanitization.
    Affected if The WL_DefaultKeyID parameter is used in an unsafe manner (passed directly to shell execution) allowing injection of arbitrary commands.

A user is affected if they have an Abode iota All-In-One Security Kit running firmware version 6.9X or 6.9Z with the XCMD testWifiAP functionality accessible and the WL_DefaultKeyID parameter handled unsafely.

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

Vendor-supplied firmware patch to implement proper input validation and use safe command execution methods (e.g., avoiding shell invocation with user-controlled parameters). Until patch is available, network segmentation and restricting device management access to trusted users is recommended.

Fix this in Iota All In One Security Kit Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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