CVE-2020-2842
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 confidenceUnauthenticated HTTP vulnerability in Oracle Depot Repair's Estimate and Actual Charges component (versions 12.1.1-12.1.3) allows remote attackers to gain unauthorized access to critical data and perform unauthorized updates/inserts/deletes. Exploitation requires human interaction, indicating a social engineering 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.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 installedQuery your Oracle E-Business Suite application inventory or check for Oracle Depot Repair module in your deployed applications. Look for Oracle E-Business Suite patches related to Depot Repair.Affected if Oracle Depot Repair version 12.1.1, 12.1.2, or 12.1.3 is installed and accessible
-
Verify the installed Depot Repair versionAccess the Oracle Depot Repair application administration interface or check the Oracle E-Business Suite version information. Look for the Estimate and Actual Charges component version information.Affected if The installed version falls within the range 12.1.1 to 12.1.3 inclusive
-
Determine if Estimate and Actual Charges component is enabledCheck the Oracle Depot Repair module configuration or component list to see if the Estimate and Actual Charges feature is activated. This is typically found in the module responsibility or feature enablement settings.Affected if The Estimate and Actual Charges component is enabled and accessible via HTTP
-
Check HTTP interface exposureReview network configuration and web server settings to confirm the Oracle Depot Repair web interface is exposed via HTTP/HTTPS. Verify whether external network access is permitted to the Depot Repair application URLs.Affected if The Depot Repair HTTP interface is reachable from network locations where untrusted users could access it
-
Inspect HTTP access logs for suspicious patternsReview web server and Oracle Apache logs for unusual HTTP requests to Estimate and Actual Charges endpoints. Look for unauthorized query parameters, unexpected POST requests, or anomalous access patterns from unfamiliar IP addresses.Affected if Unexplained or unauthorized HTTP requests targeting Estimate and Actual Charges functionality are present in logs
You are affected if Oracle Depot Repair version 12.1.1 through 12.1.3 is installed with the Estimate and Actual Charges component enabled and its HTTP interface is accessible to potential attackers.
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. Until patch is available, restrict network access to Oracle Depot Repair module via firewall or web application firewall and monitor for suspicious HTTP patterns.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2842 — 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-2842 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