dbcve.org
One To One FulfillmentApplication · Oracle

CVE-2020-14819

HIGH · 8.2 CVSS v3.1 Published 2020-10-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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). The supported version that is affected is 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.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/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 · moderate confidence

CVE-2020-14819 is an unauthenticated HTTP vulnerability in the Print Server component of Oracle One-to-One Fulfillment 12.1.3. An attacker with network access can exploit this flaw without credentials, requiring human interaction to trigger the attack. The vulnerability allows unauthorized access to critical data (high confidentiality impact) and limited unauthorized modifications (low integrity impact), potentially affecting additional products in the Oracle E-Business Suite.

MitigationApply Oracle Critical Patch Update (CPU) for October 2020 or later. As an immediate workaround, restrict network access to the Print Server via firewall rules or disable unauthenticated HTTP access until the patch can be applied. Validate all print-related configurations and monitor for unauthorized data access.

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.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. Verify Oracle One-to-One Fulfillment version
    Locate the Oracle E-Business Suite installation directory and check the version file for the One-to-One Fulfillment module, or query the Oracle applications registry for the exact version number of the Print Server component.
    Affected if The installed version is exactly 12.1.3.
  2. Confirm Print Server component is enabled
    Check the Oracle Application Manager or concurrent request manager configuration to determine if the Print Server (also known as the Print Server daemon or printosp) is active and running on the system.
    Affected if The Print Server component is enabled and running.
  3. Identify exposed HTTP listener for Print Server
    Review Oracle Net configuration and HTTP server settings to locate any HTTP endpoints that serve the Print Server functionality. Check for port entries in the application tier configuration files.
    Affected if An unauthenticated HTTP listener is configured for the Print Server on a reachable network port.
  4. Verify network accessibility
    Test network connectivity to the identified Print Server HTTP port from external networks using tools like netcat or curl. Review firewall rules and Oracle WebLogic/Apache configuration for exposed endpoints.
    Affected if The Print Server HTTP port is accessible from untrusted networks without authentication requirements.

A system is affected if Oracle One-to-One Fulfillment version 12.1.3 is installed with the Print Server component enabled and exposed via an unauthenticated HTTP listener accessible over the network.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for October 2020 or later. As an immediate workaround, restrict network access to the Print Server via firewall rules or disable unauthenticated HTTP access until the patch can be applied. Validate all print-related configurations and monitor for unauthorized data access.

Fix this in One To One Fulfillment Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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