CVE-2023-33379
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 · uneditedConnected IO v2.1.0 and prior has a misconfiguration in their MQTT broker used for management and device communication, which allows devices to connect to the broker and issue commands to other device, impersonating Connected IO management platform and sending commands to all of Connected IO's devices.
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 confidenceConnected IO v2.1.0 and prior contains a critical MQTT broker misconfiguration that allows unauthorized devices to connect and publish commands to other devices on the network, enabling complete impersonation of the management platform and mass command injection to all connected devices.
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<= 2.1.0CVSS 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 device modelAccess the device management interface or check the device label to confirm the model is Connected IO Er2000t Vz Cat1Affected if Device is not an Er2000t model - this vulnerability only affects that specific model
-
Check firmware versionLog into the device CLI or web interface and retrieve the firmware version number (typically found in System Info or About section)Affected if Firmware version is 2.1.0 or lower (any version up to and including 2.1.0)
-
Verify MQTT broker service is runningCheck if the MQTT broker service is enabled on the device - look for port 1883 (unencrypted) or 8883 (TLS) listening, or check service status via CLIAffected if MQTT broker is not running - the vulnerability only applies when the MQTT service is active
-
Inspect MQTT broker authentication configurationAccess the MQTT broker configuration file (commonly mosquitto.conf or similar) and check for 'allow_anonymous true' or missing password/file configurationAffected if Anonymous connections are permitted or no authentication is required for MQTT clients
-
Inspect MQTT client authorization settingsCheck the MQTT broker configuration for client validation settings - look for lack of ACL (access control list) rules, client certificate requirements, or username/password enforcement for publish operationsAffected if Any client can connect and publish messages without validation, or there are no authorization controls on topic subscriptions/publishes
The environment is affected if the device is an Er2000t with firmware 2.1.0 or lower AND the MQTT broker is active with default permissive settings that allow unauthenticated client connections and unrestricted message publishing.
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 dataFix the MQTT broker configuration to enforce proper authentication, authorization, and client validation to ensure only legitimate management platform clients can publish commands to devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33379 — 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-2023-33379 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