dbcve.org
GlassfishApplication · Eclipse

CVE-2022-2712

HIGH · 7.5 CVSS v3.1 Published 2023-01-27
Fix available
A fix is available. Upgrade to after 6.2.5 or later.
See remediation →
84/100
Remediation priority · High
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 versions 5.1.0 to 6.2.5, there is a vulnerability in relative path traversal because it does not filter request path starting with './'. Successful exploitation could allow an remote unauthenticated attacker to access critical data, such as configuration files and deployed application source code. This is fixed in GlassFish 7.0.0.

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

Eclipse GlassFish versions 5.1.0 to 6.2.5 contain a relative path traversal vulnerability where request paths starting with './' are not filtered, allowing unauthenticated remote attackers to access sensitive files such as configuration files and deployed application source code.

MitigationUpgrade to GlassFish 7.0.0 or later to remediate the path traversal vulnerability.

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.1.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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed GlassFish version
    Locate the GlassFish version file or check the admin console for the version number. Common locations include the version.txt file in the GlassFish root directory or the output of the asadmin version command.
    Affected if The installed version falls within the range 5.1.0 to 6.2.5 (inclusive)
  2. Confirm GlassFish web services are running and exposed
    Check if the GlassFish HTTP or HTTPS listeners are active and accessible on the configured ports (default 8080 for HTTP, 8181 for HTTPS). Verify the web container is enabled.
    Affected if Web services are running and network-accessible to potential attackers
  3. Test for path traversal vulnerability
    Send an HTTP request to the GlassFish server with a path starting with './' followed by a sensitive file path (for example, a request to ./../../config/domain.xml or similar). Observe if the server returns file contents outside the web root.
    Affected if The server returns files or content from outside the web root when using './' prefix in the request path

You are affected if GlassFish version 5.1.0 through 6.2.5 is installed, web services are exposed, and requests with './' prefixes can access files outside the web root.

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 to GlassFish 7.0.0 or later to remediate the path traversal vulnerability.

Recommended fix High confidence

GlassFish 7.0.0

  1. Backup your current GlassFish installation, including domain configurations, deployed applications, and any custom configurations
  2. Stop the running GlassFish 5.1.0 to 6.2.5 service
  3. Download GlassFish 7.0.0 from the official Eclipse Foundation distribution (eclipse.org/glassfish)
  4. Install GlassFish 7.0.0 following the standard installation procedure for your operating system
  5. Migrate your domain configurations from the backup to the new installation - review config files for any version-specific settings
  6. Redeploy your applications to the new GlassFish 7.0.0 instance
  7. Start the GlassFish 7.0.0 service
  8. Verify the path traversal vulnerability is remediated by testing that requests with './' in the path are rejected or sanitized
Caveat GlassFish 7.0.0 includes Jakarta EE 10 which may require application code changes if migrating from Java EE/Jakarta EE 8; review Jakarta EE migration guides for namespace changes from javax.* to jakarta.*

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

Fix this in Glassfish Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,960
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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