CVE-2020-2885
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 · uneditedVulnerability in the Oracle Document Management and Collaboration product of Oracle E-Business Suite (component: Attachments). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Document Management and Collaboration. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Document Management and Collaboration, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Document Management and Collaboration accessible data as well as unauthorized update, insert or delete access to some of Oracle Document Management and Collaboration accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N).
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 confidenceUnauthenticated path traversal or file inclusion vulnerability in the Attachments component of Oracle Document Management and Collaboration within E-Business Suite. Allows remote attackers to access or modify sensitive documents via HTTP requests, requiring victim interaction (e.g., clicking malicious links). The scope change indicates the attack can impact additional products beyond the vulnerable 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>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.9CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify Oracle E-Business Suite is installedCheck system inventory or running processes for Oracle E-Business Suite components. Look for Oracle application server processes and review installed Oracle product listings.Affected if Oracle E-Business Suite is present on the system
-
Confirm Document Management and Collaboration component versionQuery the Oracle application for the Document Management and Collaboration component version. This is typically available through Oracle Enterprise Manager, Oracle Application Manager, or by querying the FND_PRODUCT_GROUPS or equivalent Oracle tables.Affected if The installed version falls within >= 12.1.1 through <= 12.1.3, or >= 12.2.3 through <= 12.2.9
-
Verify Attachments component is enabledCheck if the Oracle Web Applications Desktop Integrator (WAD) or Attachments module is configured and accessible. Review the Oracle Applications Navigator or FND_MENU to confirm attachment-related functionality is active.Affected if The Attachments component is enabled and accessible to users
-
Identify exposed attachment URLsReview Oracle WebLogic or Oracle HTTP Server access logs for requests to attachment-handling endpoints. Common patterns include URLs containing /oa_servlets/, /AttachService/, or path traversal sequences.Affected if Network-accessible URLs for document attachments exist without proper access controls
-
Check for unauthenticated access to attachment functionalityTest (in an isolated test environment) whether HTTP requests to attachment endpoints can be accessed without authentication or by manipulating path parameters. Look for parameters that might allow directory traversal.Affected if Unauthenticated or path traversal requests to attachment URLs succeed without proper validation
The environment is affected if Oracle Document Management and Collaboration is running with a version between 12.1.1-12.1.3 or 12.2.3-12.2.9, the Attachments component is enabled, and the vulnerable attachment URLs are network-accessible without proper access controls.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) for January 2020 or later. If immediate patching is not feasible, restrict network access to the affected Oracle Document Management and Collaboration URLs and monitor for unusual attachment access patterns.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2885 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2885 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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