# CVE-2018-20402: Hardcoded credentials in n/a

> Safe Software FME Server includes default accounts with predictable credentials, allowing attackers to gain unauthorized access and privileges.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-r627-cr47-hvxp

## What is CVE-2018-20402?

CVE-2018-20402 is a high-severity vulnerability in n/a, published on 23 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Safe Software FME Server through 2018.1 creates and enables three additional accounts in addition to the initial administrator account. The passwords to the three accounts are the same as the usernames, which are guest, user, and author. Logging in with these accounts will grant any user the default privilege roles that were also created for each of the accounts.

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

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

It affects 1 product.


Products: Safe Fme Server.

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

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

## Is CVE-2018-20402 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-38339](https://insights.sbomify.com/CVE-2022-38339/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2022-38340](https://insights.sbomify.com/CVE-2022-38340/): Path traversal in n/a (critical 9.1)
- [CVE-2022-38342](https://insights.sbomify.com/CVE-2022-38342/): Safe Software FME Server v2021.2.5, v2022.0.0.2 and below was discovered to contain a XML External Entity (XXE) vulnerability which allows a (high 8.5)
- [CVE-2023-35801](https://insights.sbomify.com/CVE-2023-35801/): Path traversal in n/a (high 8.1)
- [CVE-2022-38341](https://insights.sbomify.com/CVE-2022-38341/): Missing authorization in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-20402 is a high-severity vulnerability in n/a, published on 23 Dec 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20402 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-20402/ (Markdown: https://insights.sbomify.com/CVE-2018-20402/index.md)
```

## Sources

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

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