Fusion MiddlewareApplication · Oracle

CVE-2010-3599

HIGH · 9.4 CVSS v2.0 Published 2011-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 Document Capture component in Oracle Fusion Middleware 10.1.3.4 and 10.1.3.5 allows remote attackers to affect integrity and availability via unknown vectors related to Import Server. NOTE: the previous information was obtained from the January 2011 CPU. Oracle has not commented on claims from the original researcher that remote attackers can overwrite arbitrary files and execute arbitrary code via a full pathname in the first argument to the WriteJPG method in the NCSECWLib ActiveX control.

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

The vulnerability exists in the NCSECWLib ActiveX control within Oracle Document Capture versions 10.1.3.4 and 10.1.3.5. The WriteJPG method improperly validates its first argument, allowing remote attackers to specify an arbitrary file path and overwrite system files, potentially leading to arbitrary code execution.

MitigationApply Oracle Critical Patch Update (January 2011) for Oracle Document Capture; alternatively, disable or remove the NCSECWLib ActiveX control and restrict network access to the Import Server component.

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

AV:N/AC:L/Au:N/C:N/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 Document Capture installation
    Check for Oracle Document Capture installation by examining common installation directories (typically under Oracle or BEA folders in Program Files) or look for the service process 'Oracle Document Capture' in Windows Services. Query the Windows registry under HKLM\SOFTWARE\Oracle for Document Capture entries.
    Affected if Oracle Document Capture version 10.1.3.4 or 10.1.3.5 is installed.
  2. Verify installed version number
    Locate the version information for Oracle Document Capture. This can typically be found in the Windows registry under HKLM\SOFTWARE\Oracle\DocumentCapture or by right-clicking the installed executable and viewing Properties > Details. Compare the exact version against 10.1.3.4 and 10.1.3.5.
    Affected if The installed version matches exactly 10.1.3.4 or 10.1.3.5.
  3. Confirm NCSECWLib ActiveX control presence
    Search for the NCSECWLib ActiveX control in the Windows registry under HKCR\CLSID for the CLSID associated with NCSECWLib (typically in the registry path for ActiveX controls). The control is commonly installed in the Oracle Document Capture bin directory as NCSECWLib.dll or similar.
    Affected if The NCSECWLib ActiveX control DLL is present on the system and registered in Windows.
  4. Check if ActiveX control is accessible in browsers
    Verify that the ActiveX control is marked as safe for scripting and initialization in the Windows registry under HKLM\SOFTWARE\Microsoft\Code Store Database\Distribution Units or within the browser's ActiveX compatibility settings. Attempt to instantiate the control via a test HTML page using its CLSID if known.
    Affected if The NCSECWLib ActiveX control is registered and not blocked by Internet Explorer security settings.

A system is affected if Oracle Document Capture version 10.1.3.4 or 10.1.3.5 is installed with the NCSECWLib ActiveX control 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (January 2011) for Oracle Document Capture; alternatively, disable or remove the NCSECWLib ActiveX control and restrict network access to the Import Server component.

Fix this in Fusion Middleware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3599 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3599 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