dbcve.org
One To One FulfillmentApplication · Oracle

CVE-2020-2827

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.1.3 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. 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 remote attacker can exploit the Print Server component in Oracle One-to-One Fulfillment (versions 12.1.1-12.1.3) via HTTP to gain unauthorized access to critical data or complete access to all accessible data, with partial unauthorized update/insert/delete capabilities. The attack requires human interaction and may impact additional products due to scope change.

MitigationApply Oracle Critical Patch Updates for the One-to-One Fulfillment Print Server component. If patches are unavailable, consider network segmentation to limit HTTP exposure to the Print Server 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

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. Identify Oracle One-to-One Fulfillment installation
    Locate the Oracle E-Business Suite installation directory and confirm the One-to-One Fulfillment module is present. Check for directories named 'FND' or 'ASF' or search for files related to One-to-One Fulfillment.
    Affected if Oracle One-to-One Fulfillment is not installed - not affected. If installed, proceed to version check.
  2. Determine installed version of One-to-One Fulfillment
    Query the Oracle applications table FND_PRODUCT_GROUPS or check the release version file in the Oracle APPL_TOP directory. Look for version numbers in the 12.1.x range.
    Affected if Installed version is between 12.1.1 and 12.1.3 (inclusive) - potentially affected. Versions outside this range are not affected by this specific CVE.
  3. Verify Print Server component is enabled
    Check the Oracle application configuration for the Print Server (often accessible via Oracle Applications Manager or by reviewing the FND_CONCURRENT_PROGRAMS and FND_CP_SERVICES tables). Confirm whether the Print Server process is running or configured to run.
    Affected if Print Server is disabled or not configured - likely not affected. If enabled and HTTP-accessible, continue to exposure check.
  4. Check HTTP exposure of Print Server
    Review web server configuration (Oracle HTTP Server or Apache) for routes serving the Print Server component (typically paths like '/OA_HTML/print' or similar). Use network scanning or review web server access logs for Print Server HTTP endpoints.
    Affected if Print Server is exposed via HTTP to untrusted networks - vulnerable to remote exploitation. If HTTP access is restricted to trusted networks only, risk is reduced.

A system is affected if it runs Oracle One-to-One Fulfillment versions 12.1.1 through 12.1.3 with the Print Server component enabled and accessible via HTTP to untrusted networks.

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

Apply Oracle Critical Patch Updates for the One-to-One Fulfillment Print Server component. If patches are unavailable, consider network segmentation to limit HTTP exposure to the Print Server and implement additional authentication layers.

Fix this in One To One Fulfillment Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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