CVE-2020-2845
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 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 confidenceVulnerability in Oracle Depot Repair's Estimate and Actual Charges component allows unauthenticated remote attackers to exploit via HTTP. The attack requires human interaction (social engineering/tricking a user) and can lead to unauthorized access to critical data (high confidentiality impact) and unauthorized modification of some data (low integrity impact). The scope change indicates the attack may impact additional products beyond Depot Repair.
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.3CVSS 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.
-
Confirm Oracle Depot Repair is installedCheck if Oracle E-Business Suite with Depot Repair module is present in your environment. This is typically part of Oracle E-Business Suite installations.Affected if Depot Repair module exists in the Oracle E-Business Suite installation
-
Identify the Depot Repair versionQuery the Oracle application version registry or check the Oracle E-Business Suite version information for the Depot Repair component. Compare the installed version against the affected range of 12.1.1 through 12.1.3.Affected if The installed version falls within >= 12.1.1 and <= 12.1.3
-
Verify Estimate and Actual Charges component is accessibleCheck if the Estimate and Actual Charges feature within Depot Repair is enabled and accessible via HTTP endpoints. Review the component configuration in Oracle Depot Repair admin settings.Affected if Estimate and Actual Charges component is enabled and exposed via HTTP
-
Check network exposure of EBS HTTP interfacesDetermine if Oracle E-Business Suite HTTP interfaces are exposed to untrusted networks. Review firewall rules and network ACLs controlling access to Oracle EBS ports.Affected if HTTP interfaces are accessible from untrusted or external networks without proper restrictions
-
Review access logs for suspicious requestsExamine HTTP access logs for unusual or unauthorized requests targeting Estimate and Actual Charges endpoints. Look for patterns indicating reconnaissance or exploitation attempts.Affected if Suspicious requests to Estimate and Actual Charges endpoints are found in logs
The environment is affected if Oracle Depot Repair version 12.1.1 through 12.1.3 is installed with the Estimate and Actual Charges component enabled and accessible via HTTP.
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 for January 2020 (or subsequent relevant patches) addressing CVE-2020-2845. Until patched, restrict network access to Oracle E-Business Suite interfaces and monitor for suspicious requests to Estimate and Actual Charges endpoints.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2845 — 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-2845 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