dbcve.org
Fusion MiddlewareApplication · Oracle

CVE-2012-3135

HIGH · 10.0 CVSS v2.0 Published 2012-07-17
Fix available
A fix is available. Upgrade to after 27.7.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 the Oracle JRockit component in Oracle Fusion Middleware 28.2.3 and before, and 27.7.2 and earlier, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors.

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

Oracle JRockit contains an unspecified vulnerability in versions 28.2.3 and prior, and 27.7.2 and earlier, that allows remote attackers to impact confidentiality, integrity, and availability via unknown attack vectors. The critical CVSS score of 10 indicates complete system compromise is possible through trivial exploitation.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for July 2012, or upgrade to a supported JRockit version receiving security updates. Note: Oracle JRockit reached end-of-life in 2018; consider migration to Oracle JDK or OpenJDK as part of remediation.

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
Fusion MiddlewareApplication
Affected:<= 27.7.2= 28.2.3

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 Oracle JRockit installation
    Run 'java -version' from the command line and examine the output for 'Oracle JRockit' or 'BEA JRockit' in the product name. Alternatively, check installation directories such as $ORACLE_HOME/jrockit or C:\Program Files\Java\jrockit for Windows systems.
    Affected if The output explicitly identifies the JVM as Oracle JRockit or BEA JRockit rather than another JDK implementation.
  2. Determine installed JRockit version number
    Run 'java -version' and note the version string displayed. The format typically shows the full version (e.g., 28.2.3 or 27.7.2). If not displayed via -version, check the jrockit version file in the installation directory or the JAR file manifest.
    Affected if A version number is returned that can be compared against the affected ranges.
  3. Compare version against affected ranges
    Match the installed version number to the following vulnerable ranges: any version 27.7.2 or earlier, or exactly version 28.2.3. Treat version strings as numerical comparison where 28.2.3 is greater than 27.7.2 but 28.2.4 and later are not affected.
    Affected if The installed version is 27.7.2 or lower, or the installed version is exactly 28.2.3.
  4. Confirm the JRockit installation is active and in use
    Verify that the identified JRockit installation is the primary JVM in use by checking JAVA_HOME environment variable, or by running 'which java' (Unix) or 'where java' (Windows) to locate the executable in use.
    Affected if The vulnerable JRockit version is the active JVM running in the environment.

If the active Oracle JRockit installation is version 27.7.2 or earlier, or exactly version 28.2.3, then the environment is affected by CVE-2012-3135.

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
Upgrade available Upgrade to a release after 27.7.2
Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for July 2012, or upgrade to a supported JRockit version receiving security updates. Note: Oracle JRockit reached end-of-life in 2018; consider migration to Oracle JDK or OpenJDK as part of remediation.

Recommended fix Moderate confidence

Oracle JRockit R28.3.x or later (post R28.2.3/27.7.2)

  1. 1. Identify the exact Oracle JRockit version currently installed by running 'java -version' or checking the installation directory
  2. 2. Navigate to Oracle's Critical Patch Updates advisory page for 2012 (or relevant Security Alert)
  3. 3. Download and apply the appropriate Oracle JRockit security patch for CVE-2012-3135
  4. 4. Alternatively, upgrade to a later Oracle JRockit release (R28.3.x or later) that includes the security fix
  5. 5. After applying the patch or upgrade, restart all Java applications using the JRockit JVM
  6. 6. Verify the version change using 'java -version' to confirm the patch was applied
Caveat Upgrade may introduce behavioral changes; test applications thoroughly in a non-production environment before deploying

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

Fix this in Fusion Middleware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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