# CVE-2023-33379: Misconfiguration in n/a

> Misconfigured MQTT broker allows devices to impersonate the management platform and send commands to other devices.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-426p-c3p2-xqhp

## What is CVE-2023-33379?

CVE-2023-33379 is a critical vulnerability in n/a, published on 4 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Connected 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.

## Which versions are affected by CVE-2023-33379?

It affects 1 product.


Products: Connectedio Er2000t-Vz-Cat1 Firmware.

## How do I fix CVE-2023-33379?

No fix has been published for CVE-2023-33379 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-33379 being exploited?

There is no known exploitation of CVE-2023-33379 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33379 and fix it if it is affected.

What it is: CVE-2023-33379 is a critical vulnerability in n/a, published on 4 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33379 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-33379/ (Markdown: https://insights.sbomify.com/CVE-2023-33379/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33379
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33379
- OSV: https://osv.dev/vulnerability/CVE-2023-33379

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-33379/
Summaries are generated and may contain mistakes; the official description above is the record.