dbcve.org
Depot RepairApplication · Oracle

CVE-2020-2850

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 Depot Repair product of Oracle E-Business Suite (component: Estimate and Actual Charges). Supported versions that are affected are 12.1.1-12.1.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Depot Repair. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Depot Repair, 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 Depot Repair accessible data as well as unauthorized update, insert or delete access to some of Oracle Depot Repair 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 confidence

Unauthenticated SQL injection or similar injection vulnerability in Oracle Depot Repair's Estimate and Actual Charges component (versions 12.1.1-12.1.3). Allows remote attackers via HTTP to access critical data and modify some data without credentials. The scope change (S:C) indicates attacks may impact additional Oracle E-Business Suite products beyond the vulnerable component.

MitigationApply the latest Oracle Critical Patch Update for Oracle E-Business Suite to address this vulnerability. Restrict network access to Oracle Depot Repair interfaces and implement WAF rules as interim controls.

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
Depot RepairApplication
Affected:>= 12.1.1, <= 12.1.3

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle Depot Repair installation
    Query the Oracle E-Business Suite version using the application version utilities (FND_GLOBAL.APPS_INITIALIZE or Oracle Application Manager). Look for the Depot Repair module in the installed modules list.
    Affected if Oracle Depot Repair module is not found in the E-Business Suite installation, then the system is not affected by this specific component vulnerability.
  2. Check Depot Repair version against affected range
    Retrieve the installed version of Oracle Depot Repair from the Oracle Applications Manager or by querying the FND_PRODUCT_INSTALLATIONS table. Compare the version to the range 12.1.1 through 12.1.3.
    Affected if The installed version is 12.1.1, 12.1.2, or 12.1.3.
  3. Verify Estimate and Actual Charges component is enabled
    Check the Oracle Depot Repair responsibilities and functions in the Oracle Application Manager. Look for the Estimate and Actual Charges function under the Depot Repair responsibility.
    Affected if The Estimate and Actual Charges component is enabled and accessible to users.
  4. Confirm HTTP accessibility of the Depot Repair interface
    Review the Oracle E-Business Suite listener configuration (Oracle HTTP Server or Oracle Web Listener). Determine if the /oa_html/ or /OA_HTML/ paths for Depot Repair are accessible over HTTP without authentication.
    Affected if The Depot Repair web interfaces are exposed over HTTP/HTTPS to untrusted networks.

A system is affected if it runs Oracle Depot Repair version 12.1.1, 12.1.2, or 12.1.3 with the Estimate and Actual Charges component enabled and accessible via HTTP.

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
Upgrade available Upgrade to a release after 12.1.3
Interim mitigation

Apply the latest Oracle Critical Patch Update for Oracle E-Business Suite to address this vulnerability. Restrict network access to Oracle Depot Repair interfaces and implement WAF rules as interim controls.

Fix this in Depot Repair 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 the upgrade done

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-2020-2850 — 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-2850 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