{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-9132 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-9132 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2017-9132 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2017-9132 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-9132/ (Markdown: https://insights.sbomify.com/CVE-2017-9132/index.md)","id":"CVE-2017-9132","markdown":"https://insights.sbomify.com/CVE-2017-9132/index.md","name":"CVE-2017-9132","record":{"aliases":["GHSA-q46w-jxf7-cpqf"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Mimosa wireless radios","requires_auth":"none","summary":"Attackers can use hard-coded credentials to access the MQTT broker, reading device messages and potentially triggering remote factory resets on connected clients.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"backhaul_radios","vendor":"mimosa"},{"product":"client_radios","vendor":"mimosa"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2017-9132","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Command injection in n/a","id":"CVE-2017-9133"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2017-9131"},"products":["n/a"],"published":"2017-05-21","related":[{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9133","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2017-9135","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":7.5,"headline":"Command injection in n/a","id":"CVE-2017-9131","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2017-9134","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2017-9136","kev_date_added":null,"published":"2017-05-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can use hard-coded credentials to access the MQTT broker, reading device messages and potentially triggering remote factory resets on connected clients.","url":"https://insights.sbomify.com/CVE-2017-9132/"}