dbcve.org
Depot RepairApplication · Oracle

CVE-2020-2847

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

Oracle Depot Repair's Estimate and Actual Charges component contains an unauthenticated HTTP vulnerability allowing remote attackers to access, modify, or delete data. The CVSS vector indicates network exploitability without credentials, requiring human interaction, with scope changes affecting additional products. The high confidentiality and low integrity impacts suggest an injection-based flaw (likely SQL or similar) enabling unauthorized data access.

MitigationApply Oracle Critical Patch Update (CPU) for Oracle E-Business Suite addressing this vulnerability. If no patch available, restrict network access to Oracle Depot Repair interfaces and implement additional authentication layers, while validating all input to prevent injection attacks.

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. Verify Oracle Depot Repair is installed
    Check for Oracle E-Business Suite installation and identify if Oracle Depot Repair module is present. Look for depot repair related application files, services, or Oracle E-Business Suite modules.
    Affected if Oracle Depot Repair component is present in the environment
  2. Confirm the installed version falls within affected range
    Query the Oracle E-Business Suite version information. In Oracle applications, this can often be found via the adident utility, version files in $APPL_TOP, or by querying FND_PRODUCT_INSTALLATIONS table.
    Affected if Installed version is >= 12.1.1 and <= 12.1.3
  3. Determine if Estimate and Actual Charges component is accessible
    Identify if the Estimate and Actual Charges web interface or service endpoint is exposed. Check Oracle Application Manager (OAM) or Oracle Applications Framework for the Depot Repair module status and accessibility.
    Affected if The Estimate and Actual Charges component is enabled and accessible via HTTP
  4. Verify HTTP interface exposure for Depot Repair
    Inspect web server configuration (Oracle HTTP Server, Oracle WebLogic) to determine if Depot Repair forms or services are exposed over HTTP without authentication. Check Oracle Fusion Middleware enterprise manager for deployed applications.
    Affected if Depot Repair HTTP interfaces are reachable without requiring authentication
  5. Review access controls on affected endpoints
    Examine Oracle E-Business Suite responsibility definitions and function security for Depot Repair. Verify whether Estimate and Actual Charges functions are protected by Oracle Applications username/password authentication.
    Affected if The Estimate and Actual Charges functionality can be accessed without valid Oracle Applications credentials

Environment is affected if Oracle Depot Repair version 12.1.1 through 12.1.3 is installed with the Estimate and Actual Charges component accessible via unauthenticated 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 Oracle Critical Patch Update (CPU) for Oracle E-Business Suite addressing this vulnerability. If no patch available, restrict network access to Oracle Depot Repair interfaces and implement additional authentication layers, while validating all input to prevent injection attacks.

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

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-2847 — 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-2847 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