dbcve.org
Glassfish ServerApplication · Oracle

CVE-2011-0807

HIGH · 10.0 CVSS v2.0 Published 2011-04-20
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click Patch available

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
Unspecified vulnerability in Oracle Sun GlassFish Enterprise Server 2.1, 2.1.1, and 3.0.1, and Sun Java System Application Server 9.1, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Administration.

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 confidence

Unspecified vulnerability in the Oracle Sun GlassFish/Sun Java System Application Server administration interface allows remote attackers to fully compromise confidentiality, integrity, and availability. The CVSS 10 score indicates trivial exploitability with no authentication required.

MitigationApply Oracle security patches (CPU April 2011); if patches are unavailable for this end-of-life software, upgrade to a supported GlassFish or Payara version and restrict admin interface to trusted networks.

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
Glassfish ServerApplication
Affected:= 2.1= 2.1.1= 3.0.1
Java System Application ServerApplication
Affected:= 9.1

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 or Sun Java System Application Server version
    Check the version by inspecting the asadmin version output, the product.version property in the admin console, or the version string in the installation directory (look in glassfish/lib/install/applications/__admingui/WEB-INF/glassfish-web.xml or similar version files). Compare against affected versions: Oracle GlassFish Server 2.1, 2.1.1, 3.0.1 or Sun Java System Application Server 9.1.
    Affected if The installed version matches 2.1, 2.1.1, 3.0.1, or 9.1 exactly.
  2. Determine if the administration interface is enabled and accessible
    Check if the admin console is running by attempting to access the GlassFish admin port (default 4848) or the Sun Java System Application Server admin port (default 4849). Also check the domain.xml configuration file for the admin-listener element to see if it is defined and bound to a network interface.
    Affected if The admin interface is enabled and responds to requests.
  3. Verify if the admin interface is exposed to untrusted networks
    Review the network listener configuration in domain.xml for the admin-listener. Check the address attribute: if set to 0.0.0.0 or a publicly-routable IP rather than localhost/127.0.0.1, the interface is network-exposed. Also verify firewall rules allow access to port 4848/4849 from untrusted sources.
    Affected if The admin interface listens on 0.0.0.0 or a non-localhost address and is accessible from untrusted networks.
  4. Confirm no authentication is required for the admin console
    Attempt to access the admin console URL (/common/index.jsf or /) on the admin port without providing credentials. The CVSS 10 score indicates no authentication is needed for exploitation.
    Affected if The admin console is accessible without requiring any authentication credentials.

A user is affected if they run Oracle GlassFish Server 2.1, 2.1.1, or 3.0.1 (or Sun Java System Application Server 9.1) with the administration interface enabled and exposed to the network without authentication controls in place.

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply Oracle security patches (CPU April 2011); if patches are unavailable for this end-of-life software, upgrade to a supported GlassFish or Payara version and restrict admin interface to trusted networks.

Recommended fix High confidence

Eclipse GlassFish 5.x or Payara Server (modern supported GlassFish distributions)

  1. 1. Identify all deployments using affected GlassFish Server versions (2.1, 2.1.1, 3.0.1) or Java System Application Server 9.1
  2. 2. Review Oracle Critical Patch Update April 2011 (http://www.oracle.com/technetwork/topics/security/cpuapr2011-301950.html) for available patches for your specific version
  3. 3. If currently on GlassFish 3.0.1, upgrade to at minimum GlassFish 3.1.2 or later which received the security fix
  4. 4. If on GlassFish 2.1.x, plan migration path as these versions are end-of-life; migrate to a supported GlassFish distribution (Eclipse GlassFish 5.x or Payara Server)
  5. 5. After upgrade, verify the administration console is not exposed to unauthenticated network access
  6. 6. Test application functionality in staging before production deployment
  7. 7. Apply any additional security hardening: disable remote admin if not needed, restrict admin interface to trusted networks
Caveat Older GlassFish 2.x applications may require code changes for compatibility with GlassFish 5.x; ensure application server compatibility testing is performed

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

Fix this in Glassfish Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA4.0 h
44.0 hours of engineering $7,640
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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