WorkflowApplication · Oracle

CVE-2020-2753

MEDIUM · 5.3 CVSS v3.1 Published 2020-04-15

Fix available

A fix is available. Upgrade to after 12.2.9 or later.

See remediation →

62/100

Remediation priority · Elevated

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Vulnerability in the Oracle Workflow product of Oracle E-Business Suite (component: Workflow Notification Mailer). Supported versions that are affected are 12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Workflow. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Workflow accessible data. CVSS 3.0 Base Score 5.3 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Technical summary

dbcve analysis · high confidence

Oracle Workflow Notification Mailer in Oracle E-Business Suite versions 12.1.3 and 12.2.3-12.2.9 contains an easily exploitable vulnerability reachable via unauthenticated HTTP requests, allowing remote attackers to perform unauthorized update, insert, or delete operations on some Oracle Workflow data with low integrity impact.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2020-2753 to the affected Oracle E-Business Suite instances, or implement network-level access restrictions to the Workflow Notification Mailer endpoints if patches cannot be immediately applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

WorkflowApplication

Affected:>= 12.2.3, <= 12.2.9= 12.1.3

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected?

dbcve checks

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

Identify Oracle E-Business Suite installation and version

Query the database for the applications version using SQL: SELECT release_name FROM apps.fnd_product_groups; or check the application tier version file $APPL_TOP/../APPL_TOP/../oracle/apps/etc/Version.txt

Affected if The version returned matches 12.1.3 or falls within 12.2.3 through 12.2.9
Determine Oracle Workflow version

Query the Oracle Workflow version via SQL: SELECT version FROM wf_version; or check the Workflow Oracle home for version information in the Workflow administrator screens

Affected if The Workflow version matches 12.1.3 or is between 12.2.3 and 12.2.9 inclusive
Verify Oracle Workflow Notification Mailer is configured

Log into Oracle Applications Manager (OAM) or check the Workflow mailer configuration files in $APPL_TOP/admin/<CONTEXT_NAME>.xml for <mailer> configuration entries

Affected if The Notification Mailer is enabled and configured in the EBS environment
Confirm network accessibility of Workflow services

Review firewall rules or load balancer configurations to determine if the Oracle E-Business Suite ports (typically 8000-8009 for HTTP, 443 for HTTPS) hosting the Workflow services are exposed to untrusted networks

Affected if The Workflow Notification Mailer endpoints are reachable from unauthenticated/untrusted network segments via HTTP/HTTPS

You are affected if Oracle Workflow version is 12.1.3 or between 12.2.3-12.2.9 AND the Notification Mailer is enabled and accessible over the network to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 12.2.9

Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) for CVE-2020-2753 to the affected Oracle E-Business Suite instances, or implement network-level access restrictions to the Workflow Notification Mailer endpoints if patches cannot be immediately applied.

Fix this in Workflow Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing4.0 h
Review / QA2.0 h

18.0 hours of engineering $3,200

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2020-2753 — 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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-2753 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2020-2753?

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.

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

At a glance

A fix existsUpgrade to after 12.2.9 or later

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 1.1%

Affects: Workflow

Remediation

Need this fixed?

Fix this in Workflow 18 hrs · Moderate

Typical engagement from $3,200

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2020-2753 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References