CVE-2013-5816
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 · uneditedUnspecified vulnerability in the Oracle GlassFish Server component in Oracle Fusion Middleware 2.1.1, 3.0.1, and 3.1.2 allows remote attackers to affect availability via unknown vectors related to Metro.
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 confidenceAn unspecified denial-of-service vulnerability in the Metro web services stack of Oracle GlassFish Server versions 2.1.1, 3.0.1, and 3.1.2 allows remote attackers to impact service availability via unknown attack vectors.
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= 2.1.1= 3.0.1= 3.1.2CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/A:P
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 GlassFish Server versionLocate the version file in the GlassFish installation directory, typically in the 'asadmin' version output or check the manifest file in the GlassFish installation directoryAffected if The installed version matches 2.1.1, 3.0.1, or 3.1.2 specifically (exact version match)
-
Confirm Metro web services stack is in useCheck if the Metro web services stack is deployed or enabled by examining the GlassFish domain configuration files (domain.xml) for Metro-related service entries or by listing deployed web servicesAffected if Metro web services stack is configured or deployed on the GlassFish instance
-
Verify network accessibility of web services endpointDetermine if GlassFish web services are exposed to network by checking the listener configuration in domain.xml or by testing external access to known web service endpointsAffected if The Metro web services endpoints are accessible from network (remote)
-
Review web services traffic for anomalous patternsMonitor GlassFish server logs and network traffic for unusual patterns that may indicate denial-of-service attempts against Metro web servicesAffected if Unusual patterns are observed in web services traffic or frequent service interruptions occur
Your environment is affected if you are running exactly Oracle GlassFish Server version 2.1.1, 3.0.1, or 3.1.2 AND the Metro web services stack is enabled and exposed to network traffic.
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 or migrate to a supported fork such as Eclipse GlassFish or Payara Server, as Oracle GlassFish 3.x is end-of-life.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5816 — 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-2013-5816 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