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

CVE-2022-33193

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 specifically focuses on the unsafe use of the `WL_WPAPSK` configuration value in the function located at offset `0x1c7d28` of firmware 6.9Z.

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 the iota All-In-One Security Kit's Wi-Fi test function (testWifiAP). The WL_WPAPSK configuration value (Wi-Fi WPA pre-shared key) is passed unsafely to system commands at firmware offset 0x1c7d28, allowing arbitrary command execution via crafted XCMD requests.

MitigationUpdate to vendor-provided patched firmware; if unavailable, restrict network access to the device and disable the testWifiAP function via configuration if possible.

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
    Confirm the device is a Goabode Iota All-In-One Security Kit by checking the device label, web interface, or administrative console for the model name
    Affected if The device is not a Goabode Iota All-In-One Security Kit - different models are not affected by this specific vulnerability
  2. Check the installed firmware version
    Access the device administrative interface or use the vendor's diagnostic tool to retrieve the firmware version. Look for a version string starting with 6.9 (such as 6.9x or 6.9z variants)
    Affected if The firmware version matches 6.9x or 6.9z, or falls within the 6.9x/6.9z version family - these are the affected versions according to the CVE
  3. Verify XCMD interface accessibility
    Check if the device's XCMD API endpoint (testWifiAP function) is accessible from the network. This is typically exposed on the device's web interface or management port
    Affected if The XCMD interface with testWifiAP function is exposed and reachable on the network - this is the attack vector for command injection
  4. Inspect WL_WPAPSK configuration handling
    If you have access to the device firmware or configuration, examine how the WL_WPAPSK (Wi-Fi WPA pre-shared key) value is processed. Look for code paths where this value is passed to system commands without proper sanitization at offset 0x1c7d28
    Affected if The device processes WL_WPAPSK values through the vulnerable code path at the specified firmware offset without input sanitization

A defender is affected if they have a Goabode Iota All-In-One Security Kit running firmware versions 6.9x or 6.9z with the testWifiAP XCMD interface accessible on the network, as this combination allows the WL_WPAPSK value to be injected with malicious commands.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to vendor-provided patched firmware; if unavailable, restrict network access to the device and disable the testWifiAP function via configuration if possible.

Recommended fix Moderate confidence

Latest firmware version available from Abode Systems (version higher than 6.9X/6.9Z)

  1. Check the current firmware version of the Iota All In One Security Kit by accessing the device web interface or using the Abode mobile app
  2. If the firmware version is 6.9X or 6.9Z, upgrade to the latest available firmware version from Abode Systems, Inc.
  3. Verify the upgrade was successful by checking the firmware version again after the update
  4. Restrict network access to the device's management interface to minimize exposure while the device is on the network
Caveat Standard firmware upgrade considerations apply - ensure stable power during update and review release notes for any configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iota All In One Security Kit Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing16.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,320
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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