# CVE-2018-16705: Information disclosure in n/a

> Unauthenticated attackers can access XML files exposing system usernames, unsalted MD5 password hashes, and cleartext SMS passwords on FURUNO FELCOM devices.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jgrg-hjm6-wj6m

## What is CVE-2018-16705?

CVE-2018-16705 is a critical vulnerability in n/a, published on 10 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FURUNO FELCOM 250 and 500 devices allow unauthenticated access to the xml/permission.xml file containing all of the system's usernames and passwords. This includes the Admin and Service user accounts and their unsalted MD5 hashes, as well as the SMS server password in cleartext.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2018-16705?

It affects 2 products.


Products: Furuno Felcom 250 Firmware, Furuno Felcom 500 Firmware.

## How do I fix CVE-2018-16705?

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

## Is CVE-2018-16705 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-16591](https://insights.sbomify.com/CVE-2018-16591/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-16590](https://insights.sbomify.com/CVE-2018-16590/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-16705 and fix it if it is affected.

What it is: CVE-2018-16705 is a critical vulnerability in n/a, published on 10 Sep 2018. 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-2018-16705 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-2018-16705/ (Markdown: https://insights.sbomify.com/CVE-2018-16705/index.md)
```

## Sources

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

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