CVE-2020-2874
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 Email Center product of Oracle E-Business Suite (component: Customer Search). 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 Email Center. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Email Center, 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 Email Center accessible data as well as unauthorized update, insert or delete access to some of Oracle Email Center 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 vulnerability in Oracle Email Center's Customer Search component (EBS 12.1.1-12.1.3) allows remote attackers via HTTP to access sensitive data and modify/delete some records. The attack requires human interaction, indicating likely social engineering to trigger the exploit.
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.
-
Identify Oracle EBS installation and versionQuery the Oracle EBS version banner or check the OA_HTML/AppsCheck version info. Run 'select release_name from apps.fnd_product_groups' if database access is available.Affected if The version returned is between 12.1.1 and 12.1.3 inclusive
-
Confirm Oracle Email Center module is enabledCheck the Oracle Applications Manager (OAM) or use FND_MODULE API to list enabled EBS modules. Look for the 'Email Center' or 'ICX' module in the enabled modules list.Affected if Email Center module appears as installed or enabled in the EBS module list
-
Verify HTTP access to Email CenterCheck the EBS context file (context_name.xml in $APPL_TOP/admin) for the 's_oa_html' or 's_web_html' entry, or test direct access to the Email Center login page URL (typically /OA_HTML/icxnap/ or similar Email Center paths).Affected if The Email Center HTTP endpoints are accessible and respond without authentication prompts
-
Confirm Customer Search component is exposedAttempt to access the Customer Search function within Email Center via HTTP, or inspect the Oracle EBS responsibility definition for Email Center to see if Customer Search function is assigned to any responsibility accessible over HTTP.Affected if The Customer Search function is accessible through a web responsibility without additional authentication controls
A user is affected if they run Oracle E-Business Suite versions 12.1.1 through 12.1.3 with Oracle Email Center's Customer Search component exposed 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 (CPU) containing the fix for CVE-2020-2874. Restrict network access to Oracle Email Center HTTP interfaces and monitor for suspicious customer search queries.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.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,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2874 — 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-2874 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