dbcve.org
Outside In TechnologyApplication · Oracle

CVE-2015-6014

HIGH · 10.0 CVSS v2.0 Published 2016-01-22
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 Outside In Technology component in Oracle Fusion Middleware 8.5.0, 8.5.1, and 8.5.2 allows local users to affect availability via unknown vectors related to Outside In Filters, a different vulnerability than CVE-2015-4808, CVE-2015-6013, CVE-2015-6015, and CVE-2016-0432. NOTE: the previous information is from the January 2016 CPU. Oracle has not commented on third-party claims that this issue is a stack-based buffer overflow in Oracle Outside In 8.5.2 and earlier, which allows remote attackers to execute arbitrary code via a crafted DOC file.

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 Outside In Technology versions 8.5.0 through 8.5.2 contain a vulnerability in the document filtering component. Third-party sources indicate this is a stack-based buffer overflow that can be triggered via a specially crafted DOC file, potentially allowing remote code execution. The CVSS score of 10 reflects critical severity with complete availability impact.

MitigationApply the January 2016 Critical Patch Update (CPU) for Oracle Fusion Middleware to address the vulnerability in Oracle Outside In. Organizations unable to patch immediately should implement input validation, sandboxing, or disable document preview functionality for untrusted DOC files.

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
Outside In TechnologyApplication
Affected:= 8.5.0= 8.5.1= 8.5.2

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 Outside In Technology installation
    Search the system for Oracle Outside In Technology libraries or executables. Check Oracle product directories, common application paths, and any bundled installations (such as Oracle WebLogic, Oracle Content Server, or Oracle Information Rights Management that embed this technology). Look for version files, DLLs, or executables with 'Outside In' in the name.
    Affected if Oracle Outside In Technology is present on the system
  2. Determine installed version of Oracle Outside In
    Locate version information for the Oracle Outside In installation. Common locations include version files in the product directory, version strings in DLL/executable properties, or Oracle inventory records. Compare the version number to the affected range: 8.5.0, 8.5.1, or 8.5.2.
    Affected if The installed version is exactly 8.5.0, 8.5.1, or 8.5.2
  3. Verify document filtering component is enabled
    Check the Oracle Outside In configuration to determine if the document filtering component is active. This is typically controlled via configuration files or registry settings that enable/disable the filtering subystem.
    Affected if Document filtering is enabled and available for processing files
  4. Confirm DOC file processing is permitted
    Examine the configuration to verify that DOC file parsing is allowed. Check for any file type restrictions or filtering rules that would prevent DOC files from being processed by the Outside In filters.
    Affected if DOC files can be processed by the filtering component

The system is affected if Oracle Outside In Technology versions 8.5.0, 8.5.1, or 8.5.2 are installed with the document filtering component enabled and DOC file processing permitted.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the January 2016 Critical Patch Update (CPU) for Oracle Fusion Middleware to address the vulnerability in Oracle Outside In. Organizations unable to patch immediately should implement input validation, sandboxing, or disable document preview functionality for untrusted DOC files.

Recommended fix Moderate confidence

Oracle Outside In Technology 8.5.3 or later (or apply January 2016 CPU patch)

  1. 1. Identify all systems running Oracle Outside In Technology versions 8.5.0, 8.5.1, or 8.5.2
  2. 2. Download and apply the Oracle Critical Patch Update (CPU) released January 2016 or later, which contains the security fix for this vulnerability
  3. 3. Alternatively, upgrade Oracle Outside In Technology to version 8.5.3 or later which contains the security fixes
  4. 4. After applying the patch/upgrade, verify the version to confirm the fix is in place
  5. 5. Re-scan or re-test any previously submitted DOC files for potential malicious content
Caveat Review Oracle patch documentation for any compatibility considerations with your specific Oracle Fusion Middleware configuration

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

Fix this in Outside In Technology Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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