CVE-2017-1000029
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 · uneditedOracle, GlassFish Server Open Source Edition 3.0.1 (build 22) is vulnerable to Local File Inclusion vulnerability, that makes it possible to include arbitrary files on the server, this vulnerability can be exploited without any prior authentication.
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 confidenceOracle GlassFish Server Open Source Edition 3.0.1 contains a Local File Inclusion (LFI) vulnerability that allows unauthenticated remote attackers to include arbitrary files on the server, potentially exposing sensitive configuration files, credentials, or source code.
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= 3.0.1CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify GlassFish versionLocate the GlassFish installation directory and check the version. Common paths include glassfish3/glassfish/lib/installer.jar or glassfish3/glassfish/domains/domain1/config/version.txt. Alternatively, access the admin console at http://localhost:4848 or check server logs for version strings.Affected if The installed version is exactly 3.0.1 (Open Source Edition)
-
Confirm server is accessible over networkCheck if GlassFish HTTP listener is bound to a non-localhost interface. Review the network listener configuration in the GlassFish admin console under Configuration > Network Config > Network Listeners, or check the domain.xml configuration file in the config directory.Affected if The server listens on 0.0.0.0 or a public IP address rather than only localhost
-
Identify exposed web endpointsReview deployed web applications and servlets. Check the web.xml descriptor in glassfish3/glassfish/domains/domain1/config/web.xml or the Sun-web.xml for each application. Look for any endpoints that handle file path parameters.Affected if Applications with file-serving or file-inclusion functionality are deployed and publicly accessible
-
Check default web.xml configurationExamine the default web.xml located in glassfish3/glassfish/lib/installer/install_dir_windows.properties or the conf directory for default servlet mappings that may permit directory traversal.Affected if Default servlet or file serving handlers allow path parameters without proper sanitization checks
You are affected if GlassFish Server Open Source Edition version 3.0.1 is running and accessible over the network with unauthenticated endpoints that handle file paths.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade to a patched version of GlassFish Server or consider migrating to a supported application server (e.g., Payara Server, which is the supported fork of GlassFish). If immediate patching is not possible, restrict access to the vulnerable endpoints at the network level.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-1000029 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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