CVE-2017-9131
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 · uneditedAn issue was discovered on Mimosa Client Radios before 2.2.3 and Mimosa Backhaul Radios before 2.2.3. By connecting to the Mosquitto broker on an access point and one of its clients, an attacker can gather enough information to craft a command that reboots the client remotely when sent to the client's Mosquitto broker, aka "unauthenticated remote command execution." This command can be re-sent endlessly to act as a DoS attack on the client.
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 confidenceMimosa Client and Backhaul Radios before version 2.2.3 have an unauthenticated Mosquitto MQTT broker that allows remote attackers to gather device information and send reboot commands to client devices, enabling unauthenticated remote command execution and denial of service.
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.2.1<= 2.2.1CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the Mimosa device model and firmware versionAccess the Mimosa radio web interface or CLI and locate the firmware version in the system status or about page. Alternatively, check the device's HTTP API endpoint for version information.Affected if The displayed firmware version is 2.2.1 or earlier (any version <= 2.2.1)
-
Confirm the device is a Mimosa Backhaul or Client RadioVerify the device type through the web interface device info, CLI output, or the product model identifier in the system settings.Affected if The device is a Mimosa Backhaul Radio or Mimosa Client Radio running the vulnerable firmware version
-
Check for exposed MQTT service on the devicePerform a network port scan against the Mimosa device looking for open port 1883 (default Mosquitto MQTT port). Use a tool such as nmap: nmap -p 1883 <device_ip>Affected if Port 1883 is open and accessible from the network, indicating the Mosquitto broker is running and exposed
-
Test MQTT broker authentication requirementsAttempt to connect to the MQTT broker on port 1883 using an MQTT client tool (such as mosquitto_client or mqttfx) without providing credentials. Subscribe to a topic or publish a test message.Affected if The MQTT broker allows anonymous (no-auth) connections and accepts commands without authentication
The device is affected if it is a Mimosa Backhaul Radio or Client Radio running firmware version 2.2.1 or earlier AND the Mosquitto MQTT broker on port 1883 is accessible without authentication.
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 dataUpgrade Mimosa firmware to version 2.2.3 or later to patch the unauthenticated Mosquitto broker vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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 $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9131 — 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-2017-9131 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