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

> Remote attackers can access sensitive data and modify the demo application via JMX RMI due to default admin credentials on port 7676.

- **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:** 16 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-q577-wwww-c57j, UBUNTU-CVE-2018-14324

## What is CVE-2018-14324?

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

### Official description

The demo feature in Oracle GlassFish Open Source Edition 5.0 has TCP port 7676 open by default with a password of admin for the admin account. This allows remote attackers to obtain potentially sensitive information, perform database operations, or manipulate the demo via a JMX RMI session, aka a "jmx_rmi remote monitoring and control problem." NOTE: this is not an Oracle supported product.

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

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

It affects 1 product.


Products: Oracle Glassfish Server.

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

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

## Is CVE-2018-14324 being exploited?

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

Public exploit code:

- Hacking Eclipse GlassFish - CVE-2018-14324 (github_poc): https://github.com/matejsmycka/CVE-2018-14324-Exploit

## Other vulnerabilities in n/a

- [CVE-2011-0807](https://insights.sbomify.com/CVE-2011-0807/): Other in n/a (critical 10.0)
- [CVE-2017-1000030](https://insights.sbomify.com/CVE-2017-1000030/): Information disclosure in n/a (critical 9.8)
- [CVE-2016-3607](https://insights.sbomify.com/CVE-2016-3607/): Other in n/a (critical 9.8)
- [CVE-2016-5528](https://insights.sbomify.com/CVE-2016-5528/): Auth bypass in GlassFish Server (critical 9.0)
- [CVE-2016-5519](https://insights.sbomify.com/CVE-2016-5519/): Other in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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