# CVE-2017-9132: Hardcoded credentials in n/a

> Attackers can use hard-coded credentials to access the MQTT broker, reading device messages and potentially triggering remote factory resets on connected clients.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q46w-jxf7-cpqf

## What is CVE-2017-9132?

CVE-2017-9132 is a high-severity vulnerability in n/a, published on 21 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A hard-coded credentials issue was discovered on Mimosa Client Radios before 2.2.3, Mimosa Backhaul Radios before 2.2.3, and Mimosa Access Points before 2.2.3. These devices run Mosquitto, a lightweight message broker, to send information between devices. By using the vendor's hard-coded credentials to connect to the broker on any device (whether it be an AP, Client, or Backhaul model), an attacker can view all the messages being sent between the devices. If an attacker connects to an AP, the AP will leak information about any clients connected to it, including the serial numbers, which can be used to remotely factory reset the clients via a page in their web interface.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2017-9132?

It affects 2 products.


Products: Mimosa Backhaul Radios, Mimosa Client Radios.

## How do I fix CVE-2017-9132?

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

## Is CVE-2017-9132 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-9133](https://insights.sbomify.com/CVE-2017-9133/): Command injection in n/a (high 8.8)
- [CVE-2017-9135](https://insights.sbomify.com/CVE-2017-9135/): Command injection in n/a (high 8.8)
- [CVE-2017-9131](https://insights.sbomify.com/CVE-2017-9131/): Command injection in n/a (high 7.5)
- [CVE-2017-9134](https://insights.sbomify.com/CVE-2017-9134/): Information disclosure in n/a (high 7.5)
- [CVE-2017-9136](https://insights.sbomify.com/CVE-2017-9136/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9132 and fix it if it is affected.

What it is: CVE-2017-9132 is a high-severity vulnerability in n/a, published on 21 May 2017. 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-2017-9132 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-2017-9132/ (Markdown: https://insights.sbomify.com/CVE-2017-9132/index.md)
```

## Sources

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

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