dbcve.org
Outside In TechnologyApplication · Oracle

CVE-2020-2787

HIGH · 7.3 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Vulnerability in the Oracle Outside In Technology product of Oracle Fusion Middleware (component: Outside In Filters). Supported versions that is affected is 8.5.4. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Outside In Technology. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Outside In Technology accessible data as well as unauthorized read access to a subset of Oracle Outside In Technology accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Outside In Technology. Note: Outside In Technology is a suite of software development kits (SDKs). The protocol and CVSS score depend on the software that uses the Outside In Technology code. The CVSS score assumes that the software passes data received over a network directly to Outside In Technology code, but if data is not received over a network the CVSS score may be lower. CVSS 3.0 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L).

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

Vulnerability in Oracle Outside In Technology's Filters component (version 8.5.4). Unauthenticated remote attackers can exploit this via HTTP to achieve unauthorized read, write, and delete access to data processed by Outside In, plus partial denial of service. The issue stems from insufficient validation in the document filtering/parsing functionality.

MitigationApply Oracle's patches for Outside In Technology 8.5.4 or upgrade to a patched version. If this SDK is embedded in custom applications, recompile with the patched Oracle library version.

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.4

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Locate Oracle Outside In Technology installation
    Search for Oracle Outside In library files (such as iSafe.dll, iffilt.dll, or the main SDK directories) on the system. Common paths include the Oracle installation directory, application bin folders, or third-party application directories where the SDK may be embedded.
    Affected if Oracle Outside In Technology files are found on the system
  2. Determine installed version of Oracle Outside In Technology
    Check the version information of the Outside In library files. Right-click the DLL file, select Properties, and view the File Version tab. Alternatively, use a command like 'dir /s *Oracle*Outside*In*' or check version info via PowerShell.
    Affected if The version reported is exactly 8.5.4
  3. Confirm Filters component is present and enabled
    Verify the Filters component module (usually named with 'filt' or 'filter' in the filename) exists within the Oracle Outside In installation directory. Check that the component is not disabled or removed.
    Affected if The Filters component file exists in the Oracle Outside In installation
  4. Check for HTTP/network exposure of the Filters component
    Review application configurations or web server settings to determine if the Oracle Outside In Filters component is exposed via HTTP. Look for web service endpoints or ISAPI filters that use Outside In for document processing.
    Affected if The Filters component is accessible via HTTP/network

A user is affected if Oracle Outside In Technology version 8.5.4 is installed with the Filters component present and exposed via HTTP, allowing remote unauthenticated attackers to exploit insufficient validation in document parsing.

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's patches for Outside In Technology 8.5.4 or upgrade to a patched version. If this SDK is embedded in custom applications, recompile with the patched Oracle library version.

Fix this in Outside In Technology Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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