CVE-2012-0551
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 Java Runtime Environment (JRE) in Oracle Java SE 7 update 4 and earlier and 6 update 32 and earlier, and the GlassFish Enterprise Server component in Oracle Sun Products Suite GlassFish Enterprise Server 3.1.1, allows remote attackers to affect confidentiality and integrity via unknown vectors related to Web Container or Deployment.
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 confidenceA remote code execution vulnerability in Oracle Java SE (versions 7u4 and earlier, 6u32 and earlier) and GlassFish Enterprise Server 3.1.1 affecting the Web Container and Deployment components. The vulnerability allows remote attackers to compromise confidentiality and integrity through unknown vectors in the JRE web container.
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.1.1<= 1.6.0= 1.6.0<= 1.7.0= 1.7.0<= 1.6.0= 1.6.0<= 1.7.0= 1.7.0= 1.6.0= 1.6.0CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- None
AV:N/AC:M/Au:N/C:P/I:P/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.
-
Check Java versionRun 'java -version' or 'javac -version' to see the installed JRE/JDK versionAffected if Version shows 1.6.0, 1.7.0, or any version earlier than 1.6.0 or 1.7.0 (versions prior to 1.6.0 Update 33 or 1.7.0 Update 5)
-
Check GlassFish Server versionLook for GlassFish installation and check version. Typically found via admin console, version.txt, or asadmin version commandAffected if GlassFish Enterprise Server version is exactly 3.1.1
-
Identify Web Container statusIn GlassFish, check if the Web Container (also called web container or HTTP listener) is enabled. This can be verified through the admin console or by listing enabled components via asadmin list-commandsAffected if Web Container component is enabled and running on GlassFish 3.1.1 with vulnerable Java versions
-
Identify Deployment component statusCheck if the Deployment component is enabled in GlassFish. This is typically a built-in component but verify through admin console or asadmin list-applicationsAffected if Deployment component is enabled and GlassFish is running the vulnerable version combination
Environment is affected if running Oracle Java SE 1.6.0 or 1.7.0 (or earlier) OR GlassFish Enterprise Server 3.1.1 with the Web Container or Deployment components enabled.
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 Java SE 7 Update 5 or later, Java SE 6 Update 33 or later, or apply Oracle Critical Patch Updates. For GlassFish Enterprise Server, apply corresponding security patches or upgrade to a supported version.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0551 — 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-2012-0551 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