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

> Attackers can use the hidden mateidu account's default password to gain root shell access via SSH on Ceragon FibeAir IP-10 devices.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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-xg3x-5qg6-qvm9

## What is CVE-2017-9137?

CVE-2017-9137 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

Ceragon FibeAir IP-10 wireless radios through 7.2.0 have a default password of mateidu for the mateidu account (a hidden user account established by the vendor). This account can be accessed via both the web interface and SSH. In the web interface, this simply grants an attacker read-only access to the device's settings. However, when using SSH, this gives an attacker access to a Linux shell. NOTE: the vendor has commented "The mateidu user is a known user, which is mentioned in the FibeAir IP-10 User Guide. Customers are instructed to change the mateidu user password. Changing the user password fully solves the vulnerability."

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Ceragon Fiberair Ip-10 Firmware.

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

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

## Is CVE-2017-9137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-9137 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-9137 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-9137/ (Markdown: https://insights.sbomify.com/CVE-2017-9137/index.md)
```

## Sources

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

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