dbcve.org
GlassfishApplication · Eclipse

CVE-2024-9408

CRITICAL · 9.8 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 →
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 since version 6.2.5 it is possible to perform a Server Side Request Forgery attack in specific endpoints.

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

In Eclipse GlassFish since version 6.2.5, specific endpoints are vulnerable to Server Side Request Forgery (SSRF), allowing attackers to induce the server to make arbitrary requests to internal or external resources. This could enable access to internal services, cloud metadata endpoints, or port scanning of internal infrastructure.

MitigationRestrict network access to vulnerable endpoints, implement URL validation and allowlists for any endpoint functionality that accepts user-supplied URLs, and apply network segmentation to limit the impact of potential SSRF exploitation.

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:= 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. Confirm GlassFish version
    Check the version of your Eclipse GlassFish installation. In the GlassFish admin console, navigate to 'General Information' or run 'asadmin version'. Alternatively, check the glassfish/lib/install/applications/__admingui/war' directory or the 'product-info.properties' file in the glassfish/modules directory.
    Affected if The installed version is exactly 6.2.5 (or falls within any future affected version ranges not yet specified).
  2. Identify endpoints accepting user-supplied URLs
    Review your deployed applications and GlassFish configuration for any endpoints that accept URLs as input parameters. This includes REST APIs, webhook callbacks, URL preview features, or any functionality that makes outbound requests based on user input.
    Affected if Any endpoint in your GlassFish deployment accepts user-controlled URLs without strict allowlist validation.
  3. Check network exposure of vulnerable endpoints
    Examine the network accessibility of your GlassFish server. Determine if the endpoints are exposed to untrusted networks or the public internet. Review the 'network-config' and 'protocol' sections in the domain.xml configuration file.
    Affected if Endpoints accepting URLs are reachable from untrusted networks or the internet without authentication or IP restrictions.
  4. Review URL validation configuration
    Inspect your application's configuration and code for URL validation logic. Check if any allowlists or URL restrictions are implemented for endpoints that make outbound requests. Look for patterns like whitelist validation, hostname restrictions, or blocked IP ranges.
    Affected if No URL allowlist or validation is implemented for endpoints that accept user-supplied URLs.

You are affected if you are running Eclipse GlassFish version 6.2.5 AND have endpoints exposed that accept user-supplied URLs without proper validation or network restrictions.

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

Restrict network access to vulnerable endpoints, implement URL validation and allowlists for any endpoint functionality that accepts user-supplied URLs, and apply network segmentation to limit the impact of potential SSRF exploitation.

Recommended fix Moderate confidence

Eclipse GlassFish 7.0.0 or later

  1. 1. Backup your current GlassFish configuration and application data
  2. 2. Download the latest stable Eclipse GlassFish release (version 7.0.0 or later) from the official Eclipse Foundation website
  3. 3. Stop the currently running GlassFish 6.2.5 instance
  4. 4. Install the new GlassFish version to the same or a new directory
  5. 5. Migrate your configuration files (domain.xml, login.conf, etc.) from the old installation to the new one
  6. 6. Redeploy all applications to the new GlassFish instance
  7. 7. Start the new GlassFish server and verify all applications are functioning correctly
  8. 8. Test that the SSRF vulnerability is no longer present by validating that the affected endpoints no longer make unexpected server-side requests
Caveat Minor configuration adjustments may be required when migrating from 6.2.5 to 7.0.0; review the release notes for any deprecated APIs or configuration changes

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

Fix this in Glassfish Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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