dbcve.org
GlassfishApplication · Eclipse

CVE-2024-10031

MEDIUM · 5.4 CVSS v3.1 Published 2025-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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 version 7.0.15 is possible to perform Stored Cross-site Scripting attacks by modifying the configuration file in the underlying operating system.

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

Eclipse GlassFish 7.0.15 is vulnerable to stored cross-site scripting (XSS) through modification of configuration files at the operating system level. The application does not properly sanitize or encode values read from configuration files before rendering them in web interfaces, allowing attackers to inject malicious scripts that persist on the server.

MitigationImplement output encoding/sanitization when rendering configuration values in web interfaces, or update to a patched version of GlassFish if available. Review all configuration file parsing and display paths for proper input validation.

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:= 7.0.15

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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 if Eclipse GlassFish is installed
    Locate the GlassFish installation directory and check for the version. Common paths include /opt/glassfish, /usr/local/glassfish, or C:\glassfish on Windows. Look for a version.txt file or check the glassfish/lib/as-boot.jar manifest. Alternatively, run: asadmin version or check the product.conf file in the glassfish/etc directory.
    Affected if The installed version is Eclipse GlassFish 7.0.15 exactly.
  2. Confirm the admin web console is accessible
    Check if the GlassFish admin console port is open and responding. Default ports are 4848 (HTTP) or 8181 (HTTPS). Run: netstat -an | grep -E '4848|8181' or curl -s -o /dev/null -w '%{http_code}' http://localhost:4848. Also verify the console is enabled in domain.xml under <admin-service>.
    Affected if The GlassFish admin console is enabled and accessible on the network.
  3. Examine configuration files for unsanitized content
    Inspect key configuration files that the web console reads from: domain.xml (typically in glassfish/domains/domain1/config/), domain-cheetah.xml, and any custom configuration files. Look for script tags, javascript: URLs, or event handlers (onload, onerror, onmouseover) within attribute values.
    Affected if Configuration files contain HTML, script tags, or JavaScript event handlers that could execute when rendered in the admin console.
  4. Review as-admin command outputs for XSS patterns
    Run asadmin get commands to retrieve configuration values that are displayed in the web interface. Check output for unexpected HTML entities or script content: asadmin list --user admin --passwordfile=/tmp/pw.txt '*' | grep -i 'script\|javascript\|<img\|onerror\|onload'.
    Affected if Any configuration values retrieved via asadmin contain raw HTML or script elements.

You are affected if you are running Eclipse GlassFish version 7.0.15 with the admin web console enabled and configuration files contain unencoded HTML or script content that would render in the browser.

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

Implement output encoding/sanitization when rendering configuration values in web interfaces, or update to a patched version of GlassFish if available. Review all configuration file parsing and display paths for proper input validation.

Recommended fix Moderate confidence

Eclipse GlassFish 7.0.17 or later (latest 7.x release)

  1. 1. Identify the current Eclipse GlassFish installation version by checking the release notes or admin console
  2. 2. Navigate to the official Eclipse GlassFish download page or GitHub releases at https://github.com/eclipse-ee4j/glassfish
  3. 3. Download the latest stable release of Eclipse GlassFish 7.x (currently 7.0.17 or later)
  4. 4. Backup the current GlassFish installation, including the domain.xml configuration file and all deployed applications
  5. 5. Stop the GlassFish domain using: asadmin stop-domain domain1
  6. 6. Install the new version to replace the existing installation
  7. 7. Restore the backed up configuration files to the new installation
  8. 8. Start the domain using: asadmin start-domain domain1
Caveat Minor: Review release notes for any configuration or API changes between 7.0.15 and the target version; ensure deployed applications remain compatible

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
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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