dbcve.org
One To One FulfillmentApplication · Oracle

CVE-2020-2870

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.2.9 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 One-to-One Fulfillment product of Oracle E-Business Suite (component: Print Server). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle One-to-One Fulfillment. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle One-to-One Fulfillment, 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 One-to-One Fulfillment accessible data as well as unauthorized update, insert or delete access to some of Oracle One-to-One Fulfillment 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

Unauthenticated HTTP vulnerability in Oracle One-to-One Fulfillment Print Server component allows remote attackers to achieve high confidentiality impact (data access) and low integrity impact (partial data modification) due to scope change. Exploitation requires human interaction (victim must click/link), making it a social engineering-dependent attack against the print fulfillment system.

MitigationApply Oracle Critical Patch Update (April 2020) addressing CVE-2020-2870. If patching is not immediately feasible, restrict network access to the Print Server interface and implement additional authentication layers.

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
One To One FulfillmentApplication
Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.9

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. Confirm Oracle One-to-One Fulfillment is installed
    Locate the Oracle application directory or check for 'Oracle One-to-One Fulfillment' in installed programs/database inventory. Look for the print server component (often in Oracle Applications or Oracle E-Business Suite paths).
    Affected if The software is present on the system and the Print Server component is enabled.
  2. Identify the installed version number
    Check the Oracle One-to-One Fulfillment version through the application's about page, Oracle Applications Manager (OAM), or by querying the database FND_VERSION package. Common paths: $FND_TOP/../oracle/apps/ferp/ or via SQL: SELECT version FROM apps.fnd_product_groups WHERE product='FTE'.
    Affected if The installed version falls within 12.1.1 to 12.1.3 inclusive OR 12.2.3 to 12.2.9 inclusive.
  3. Verify the Print Server HTTP interface is exposed
    Check Oracle Print Server configuration files (typically in $FTE_TOP or context file) for HTTP listener settings. Look for entries enabling the HTTP port (often port 8000-8010 range) or check if the Print Server web module is deployed and accessible.
    Affected if The Print Server HTTP interface is enabled and listening on a network-accessible port.
  4. Assess network accessibility of the Print Server
    From an external host or non-internal network segment, attempt to reach the Print Server HTTP endpoint (e.g., curl http://target:port/print). Check firewall rules, Oracle Web Listener configuration, and Oracle E-Business Suite ports definition.
    Affected if The Print Server HTTP port is accessible from untrusted networks or does not require authentication.

A system is affected if Oracle One-to-One Fulfillment with Print Server is installed, the version is 12.1.1-12.1.3 or 12.2.3-12.2.9, and the HTTP Print Server interface is network-accessible without additional authentication.

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.2.9
Interim mitigation

Apply Oracle Critical Patch Update (April 2020) addressing CVE-2020-2870. If patching is not immediately feasible, restrict network access to the Print Server interface and implement additional authentication layers.

Fix this in One To One Fulfillment Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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