dbcve.org
Outside In TechnologyApplication · Oracle

CVE-2015-6013

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-6014, 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 WK4 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 · high confidence

This is a stack-based buffer overflow vulnerability in Oracle Outside In Technology's WK4 filter, affecting versions 8.5.2 and earlier in Oracle Fusion Middleware 8.5.0, 8.5.1, and 8.5.2. The vulnerability allows remote attackers to execute arbitrary code via a specially crafted WK4 file.

MitigationUpgrade Oracle Outside In Technology to a patched version or apply Oracle Critical Patch Updates (CPUs) that address this vulnerability.

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 for the Outside In Technology DLLs or executable files on the system, typically found in Oracle Fusion Middleware installation directories or Oracle Content Server paths. Check for files named 'wk4filt.dll' or similar WK4 filter components.
    Affected if Oracle Outside In Technology version is 8.5.0, 8.5.1, or 8.5.2 as shown in file properties or version info.
  2. Determine the installed version number
    Locate version documentation, README files, or use system utilities to query the version of the Oracle Outside In Technology installation. Compare against the affected range of 8.5.0 through 8.5.2.
    Affected if The installed version is exactly 8.5.0, 8.5.1, or 8.5.2.
  3. Verify WK4 filter is present and enabled
    Inspect the Oracle Outside In Technology filter directory to confirm the WK4 filter component exists and is loaded by the system. Check if the filter is registered and accessible to applications using Outside In Technology.
    Affected if The WK4 filter module is present and accessible in the Oracle Outside In Technology installation.
  4. Check for Oracle Fusion Middleware version
    If Oracle Fusion Middleware is installed, determine its version by checking the Oracle inventory, installation logs, or using Oracle opatch commands. The vulnerability affects Fusion Middleware versions 8.5.0, 8.5.1, and 8.5.2.
    Affected if Oracle Fusion Middleware version is 8.5.0, 8.5.1, or 8.5.2 with the affected Outside In Technology components.

The environment is affected if Oracle Outside In Technology version is 8.5.0, 8.5.1, or 8.5.2 and the WK4 filter component is present and accessible to process WK4 files.

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

Upgrade Oracle Outside In Technology to a patched version or apply Oracle Critical Patch Updates (CPUs) that address this vulnerability.

Recommended fix Moderate confidence

Upgrade to Oracle Outside In Technology 8.5.3 or later (fixed in January 2016 CPU)

  1. 1. Identify all systems running Oracle Outside In Technology versions 8.5.0, 8.5.1, or 8.5.2
  2. 2. Download the latest Oracle Outside In Technology patch from Oracle Support (refer to Oracle Critical Patch Update January 2016)
  3. 3. Apply the patch following Oracle's standard patch installation procedures
  4. 4. Verify the patch was applied successfully by checking the version number
  5. 5. Test the patched version with your document processing workflows to ensure functionality
Caveat Oracle patch upgrades typically include cumulative fixes; review Oracle patch notes for any specific compatibility concerns before deployment

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

Fix this in Outside In Technology Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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