dbcve.org
GlassfishApplication · Eclipse

CVE-2023-5763

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-03
Fix available
A fix is available. Upgrade to after 6.2.5 or later.
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
In Eclipse Glassfish 5 or 6, running with old versions of JDK (lower than 6u211, or < 7u201, or < 8u191), allows remote attackers to load malicious code on the server via access to insecure ORB listeners.

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 · moderate confidence

This is a deserialization vulnerability in Eclipse Glassfish 5 and 6 where insecure ORB (Object Request Broker) listeners allow remote attackers to inject malicious serialized objects. When running on JDK versions prior to 6u211, 7u201, or 8u191 (which lack patches for CVE-2018-11784 and similar deserialization flaws), remote code execution is possible via crafted object payloads sent to the ORB listener.

MitigationUpgrade the JDK to version 6u211+, 7u201+, or 8u191+ or later to patch the underlying deserialization vulnerabilities. Additionally, secure or disable insecure ORB listeners if not required.

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
GlassfishApplication
Affected:>= 5.0.0, <= 6.2.5

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.1/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. Identify installed Glassfish version
    Run 'asadmin version' or inspect the glassfish/lib/install/applications/__admingui/war file for the version, or check the product.xml in the Glassfish installation directory
    Affected if The version is >= 5.0.0 and <= 6.2.5
  2. Check JDK version in use
    Run 'java -version' from the command line or check the JAVA_HOME environment variable, then inspect the full version string including update number
    Affected if JDK version is prior to 6u211, 7u201, or 8u191 (or any version earlier than these patch levels)
  3. Verify ORB listener configuration
    Examine the domain.xml configuration file in Glassfish's domain/config directory, specifically looking for <orb> or <iiop-listener> elements under the <server-config> or <default-config> sections
    Affected if An ORB/IIOP listener is enabled and configured with an insecure (non-SSL) transport layer

You are affected if running Glassfish 5.0.0 through 6.2.5 with a vulnerable JDK version (pre-6u211/7u201/8u191) and with an active ORB listener configuration present in domain.xml.

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
Upgrade available Upgrade to a release after 6.2.5
Interim mitigation

Upgrade the JDK to version 6u211+, 7u201+, or 8u191+ or later to patch the underlying deserialization vulnerabilities. Additionally, secure or disable insecure ORB listeners if not required.

Recommended fix Moderate confidence

Glassfish 7.0.0 or later (with JDK 8u191+, 7u201+, or 6u211+)

  1. 1. Identify your current Glassfish version by checking the Glassfish administration console or running: asadmin version
  2. 2. Identify your current JDK version by running: java -version
  3. 3. If running JDK 8, upgrade to JDK 8u191 or later; if running JDK 7, upgrade to 7u201 or later; if running JDK 6, upgrade to 6u211 or later
  4. 4. Alternatively, upgrade Glassfish to version 7.0.0 or later which addresses this vulnerability
  5. 5. After upgrading, restart the Glassfish domain: asadmin restart-domain domain1
  6. 6. Verify the ORB listener configuration is secure by checking the ORB settings in the administration console under Configuration > ORB
Caveat Upgrading to Glassfish 7 may require compatibility testing as it is a major version change with potential API differences from versions 5.x and 6.x

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

Fix this in Glassfish Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-5763 — 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-2023-5763 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