CVE-2024-9342
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 · uneditedIn Eclipse GlassFish versions before 8.0.3 it is possible to perform Login Brute Force attacks as there is no limitation in the number of failed login attempts. GlassFish 8.0.3 adds automatic attack protection documented in https://glassfish.org/docs/latest/security-guide.html#brute-force-attack-protection .
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 confidenceEclipse GlassFish versions before 8.0.3 lack brute force attack protection, allowing unlimited failed login attempts on the admin console and other authentication endpoints. This enables attackers to systematically guess credentials without any account lockout or rate limiting, potentially leading to unauthorized administrative access.
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= 7.0.16CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GlassFish versionRun 'asadmin version' from the GlassFish bin directory, or check the glassfish/lib/asenv.bat/asenv file for version information, or inspect the glassfish-*.jar file in the lib directoryAffected if Version is 7.0.16 or any version below 8.0.3
-
Verify admin console is accessibleAttempt to access the GlassFish admin console URL (typically http://localhost:4848 or https://localhost:4848) from a browser or curl commandAffected if Admin console responds and presents a login form
-
Confirm no rate limiting on authentication endpointsReview the domain.xml configuration file (in glassfish/domains/domain1/config/domain.xml) for any <security> or <login-config> elements that enforce account lockout or rate limiting. Also check web.xml for any login-related constraints.Affected if No account-lockout, max-failures, or rate-limiting elements are present in the authentication configuration
-
Test login failure behaviorSend multiple failed login attempts to the admin console endpoint (e.g., using curl or a script to POST credentials repeatedly) and observe whether attempts are throttled, delayed, or blockedAffected if Failed login attempts are accepted without any delay, throttling, or account lockout after repeated failures
The environment is affected if running GlassFish version 7.0.16 or earlier with the admin console accessible and no account lockout or rate limiting configured on authentication endpoints.
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 to GlassFish 8.0.3 or later, which includes built-in automatic brute force attack protection as documented in the security guide.
GlassFish 8.0.3 or later
- Upgrade Eclipse GlassFish to version 8.0.3 or later to obtain the built-in brute force attack protection
- After upgrading, verify that brute force attack protection is enabled by default per the security guide at https://glassfish.org/docs/latest/security-guide.html#brute-force-attack-protection
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-9342 — 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-2024-9342 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