CVE-2017-1000030
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 Java Key Store Password Disclosure vulnerability, that makes it possible to provide an unauthenticated attacker plain text password of administrative user and grant access to the web-based administration interface.
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 is vulnerable to a Java Key Store (JKS) password disclosure vulnerability that allows unauthenticated attackers to obtain the plaintext password of administrative users, enabling unauthorized access to the web-based administration interface.
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
- High
- Availability
- High
CVSS:3.0/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm GlassFish installation versionIdentify the installed version of Oracle GlassFish Server Open Source Edition. This can typically be found in the product documentation, installation directory, or by accessing the admin console and reviewing the server version information.Affected if The installed version is exactly 3.0.1 (no other versions are affected by this specific CVE).
-
Verify admin console is network-accessibleDetermine if the GlassFish administration console (typically on port 4848) is exposed to network access. This can be checked by reviewing firewall rules, network configuration, or attempting to access the admin console URL from an untrusted network.Affected if The admin console is reachable from untrusted networks, as this enables the unauthenticated attacker to exploit the password disclosure.
-
Locate Java Key Store filesIdentify if JKS keystore files exist on the system. These are the files that store the administrative credentials in encrypted form. The vulnerability specifically allows disclosure of passwords from these keystores.Affected if JKS keystore files containing administrative credentials are present on the system, as these are the target of the password disclosure flaw.
A user is affected only if they are running exactly GlassFish Server Open Source Edition version 3.0.1 with an exposed administration interface and JKS keystore files present.
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.
dbcve · scopedUpgrade from GlassFish 3.0.1 to a supported, patched version. If upgrade is not feasible, restrict network access to the administration interface to trusted IPs and implement additional authentication controls such as VPN or multi-factor authentication.
Eclipse GlassFish 5.1.0 or latest stable 5.x/6.x release
- 1. Identify all GlassFish 3.0.1 installations in your environment
- 2. Back up all configuration files, domain.xml files, and the domain directory
- 3. Download Eclipse GlassFish 5.1.0 (or latest 5.x/6.x stable release) from https://projects.eclipse.org/projects/ee4j.glassfish/downloads
- 4. Install the new GlassFish version on a separate system or staging environment
- 5. Migrate your application deployments, domain configurations, and resource configurations from GlassFish 3.0.1 to the new version
- 6. Change the admin password immediately after migration using the asadmin command: asadmin change-admin-password
- 7. Ensure the new admin console is accessible only over HTTPS by configuring SSL/TLS
- 8. Review and update any authentication or authorization settings to align with current security best practices
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000030 — 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-1000030 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