dbcve.org
Glassfish ServerApplication · Oracle

CVE-2018-14324

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Oracle GlassFish Open Source Edition 5.0 demo feature exposes JMX RMI on TCP port 7676 by default with a hardcoded admin credential (admin/admin), allowing remote unauthenticated attackers to access sensitive information, execute database operations, and manipulate the application via JMX RMI sessions.

MitigationDisable the demo feature in GlassFish 5.0, change the default admin password to a strong unique value, and block or restrict access to port 7676 via firewall rules or network segmentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Glassfish ServerApplication
Affected:= 5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GlassFish version
    Locate and inspect the GlassFish installation to determine the exact version number (for example, check version files in the installation directory or use asadmin version command)
    Affected if The installed version is Oracle GlassFish Server 5.0 exactly
  2. Identify if demo feature is enabled
    Inspect the GlassFish domain configuration for demo-related settings (typically in domain.xml or through asadmin get commands for demo/enable properties)
    Affected if The demo feature or sample application service is enabled in the configuration
  3. Verify port 7676 is listening
    Check network listening ports on the GlassFish host using commands such as netstat, ss, or nmap to see if TCP port 7676 is open and accepting connections
    Affected if TCP port 7676 is open and bound to a JMX RMI service
  4. Test default credential accessibility
    Attempt to authenticate to the JMX RMI service on port 7676 using the hardcoded credentials admin/admin
    Affected if The default admin/admin credentials successfully authenticate to the JMX RMI interface

A system is affected if it runs GlassFish 5.0 with the demo feature enabled, has port 7676 exposed, and retains the default admin credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable the demo feature in GlassFish 5.0, change the default admin password to a strong unique value, and block or restrict access to port 7676 via firewall rules or network segmentation.

Recommended fix Moderate confidence

Eclipse GlassFish 7.0 or latest stable release

  1. 1. Download the latest Eclipse GlassFish release (e.g., Eclipse GlassFish 7.0 or later) from https://glassfish.org/download
  2. 2. Install the new GlassFish version on your target environment
  3. 3. Migrate your application configurations, domain.xml settings, and deployed applications from GlassFish 5.0 to the new version
  4. 4. Configure new admin credentials using the `asadmin` command: `asadmin change-admin-password`
  5. 5. Ensure port 7676 (JMX/RMI) is not exposed publicly; configure network bindings in domain.xml to bind only to localhost if needed
  6. 6. Start the new GlassFish instance and verify all applications function correctly
  7. 7. Remove or securely decommission the old GlassFish 5.0 installation
Caveat Migration from Oracle GlassFish 5.0 to Eclipse GlassFish may require changes to namespace declarations (javax.* to jakarta.*) for Jakarta EE 9+ compatibility, and some deprecated APIs may need updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glassfish Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-14324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-14324 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data