CVE-2017-9133
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. In the device's web interface, after logging in, there is a page that allows you to ping other hosts from the device and view the results. The user is allowed to specify which host to ping, but this variable is not sanitized server-side, which allows an attacker to pass a specially crafted string to execute shell commands as the root user.
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 confidenceThe ping functionality in Mimosa Client and Backhaul Radio web interfaces before version 2.2.3 lacks server-side input sanitization, allowing an authenticated attacker to inject OS commands through the ping host parameter and execute them with root privileges.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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 the device as a Mimosa radioAccess the device web interface or check the device label/documentation to confirm it is a Mimosa Backhaul Radio or Mimosa Client Radio. Note the model number if visible.Affected if The device is a Mimosa Backhaul Radio or Mimosa Client Radio and the firmware version is 2.2.1 or earlier.
-
Determine the firmware versionLog into the Mimosa radio web interface and navigate to the status or system information page to view the installed firmware version. Alternatively, check the device dashboard or about section for the firmware build number.Affected if The firmware version displayed is 2.2.1 or any version lower than 2.2.3.
-
Verify ping functionality is accessibleLocate the ping or network diagnostics tool within the Mimosa web interface. Confirm the ping feature is present and available for use by an authenticated user.Affected if The ping feature is accessible to authenticated users on the device.
-
Confirm web interface authentication is enabledCheck the device security settings to ensure the web management interface requires authentication. Verify that user accounts exist and login is required to access device functions.Affected if The web interface permits authenticated access, as the vulnerability requires an authenticated attacker.
The environment is affected if the device is a Mimosa Backhaul Radio or Client Radio running firmware version 2.2.1 or earlier, with the ping feature accessible to authenticated users.
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 radio firmware to version 2.2.3 or later to patch the command injection vulnerability. As a compensating control, restrict access to the device web interface to trusted networks until the update can be applied.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9133 — 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-9133 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