dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022. Known ransomware use
Fusion MiddlewareApplication · Oracle

CVE-2012-1710

CRITICAL · 9.8 CVSS v3.1 Published 2012-05-03
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware 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 the Oracle WebCenter Forms Recognition component in Oracle Fusion Middleware 10.1.3.5 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Designer, a different vulnerability than CVE-2012-1709.

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

CVE-2012-1710 is an unspecified critical vulnerability in Oracle WebCenter Forms Recognition 10.1.3.5 affecting the Designer component, allowing remote attackers to fully compromise confidentiality, integrity, and availability. The vulnerability is exploitable remotely with no authentication required, as indicated by the CVSS 9.8 score. This is distinct from the related CVE-2012-1709.

MitigationApply the Oracle Critical Patch Update from June 2012 that addresses this vulnerability; if the product is no longer supported, consider upgrading to a supported Oracle WebCenter version or decommissioning the legacy system.

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:= 10.1.3.5

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Fusion Middleware version
    Locate the Oracle Fusion Middleware installation directory and check the version file or use Oracle inventory commands. Common locations include the ORACLE_HOME directory or registry entries for installed Oracle products.
    Affected if The installed version is exactly 10.1.3.5
  2. Confirm WebCenter Forms Recognition installation
    Check for the presence of Oracle WebCenter Forms Recognition component within the Fusion Middleware installation. Look for directories or services named 'Forms Recognition' or 'Frmr' in the Oracle home structure.
    Affected if WebCenter Forms Recognition is installed on the system
  3. Verify Designer component is present
    Inspect the WebCenter Forms Recognition installation for the Designer component. Check for Designer-related executables, services, or web applications within the Forms Recognition directory structure.
    Affected if The Designer component is installed and present on the system
  4. Check Designer service accessibility
    Identify any network services or web endpoints associated with the Forms Recognition Designer component. Review application server configurations, port bindings, and any exposed interfaces.
    Affected if The Designer component has an accessible network service or interface
  5. Review Designer configuration files
    Examine configuration files within the WebCenter Forms Recognition Designer directory for any unusual settings, custom handlers, or processing configurations that could indicate exploitation.
    Affected if Configuration files show unexpected modifications or custom settings

A system is affected if Oracle Fusion Middleware version 10.1.3.5 is installed with the WebCenter Forms Recognition Designer component present and accessible.

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 the Oracle Critical Patch Update from June 2012 that addresses this vulnerability; if the product is no longer supported, consider upgrading to a supported Oracle WebCenter version or decommissioning the legacy system.

Recommended fix Moderate confidence

Oracle Fusion Middleware 11g or 12c (supported versions with security patches)

  1. 1. Identify current Oracle Fusion Middleware 10.1.3.5 deployment components and dependencies
  2. 2. Plan migration to a supported Oracle Fusion Middleware version (11g or 12c series, which received patches for this vulnerability)
  3. 3. Request Oracle Critical Patch Update (CPU) patches from Oracle Support for July 2012 if immediate mitigation on legacy system is required
  4. 4. Apply Oracle CPU July 2012 patches to the WebCenter Forms Recognition component
  5. 5. Verify the patches were applied successfully and test functionality
  6. 6. Schedule full upgrade to supported Fusion Middleware version as legacy 10.1.3.x is end-of-life
Caveat Legacy 10.1.3.x applications may require code modifications for compatibility with newer Fusion Middleware versions; Oracle 10.1.3.x is end-of-life with no official support

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

Fix this in Fusion Middleware Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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