dbcve.org
One To One FulfillmentApplication · Oracle

CVE-2021-2101

CRITICAL · 9.1 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle One-to-One Fulfillment. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle One-to-One Fulfillment accessible data as well as unauthorized access to critical data or complete access to all Oracle One-to-One Fulfillment accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 the Print Server component of Oracle One-to-One Fulfillment (E-Business Suite) allows remote attackers to create, delete, or modify critical data, as well as access all data in the system. The attack requires no authentication, no user interaction, and has low complexity, with high confidentiality and integrity impacts.

MitigationApply Oracle Critical Patch Update (CPU) security patches for CVE-2021-2101. If immediate patching is not possible, restrict network access to the One-to-One Fulfillment Print Server via firewall or network segmentation to prevent unauthenticated HTTP 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.1, <= 12.1.3>= 12.2.3, <= 12.2.10

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 and confirm the One-to-One Fulfillment module is present. Check the application's inventory or modules list.
    Affected if Oracle One-to-One Fulfillment module is installed and running
  2. Determine the installed version
    Query the installed version of Oracle One-to-One Fulfillment using Oracle's standard version retrieval methods (such as AD utilities or module inventory queries). Compare the version against the affected ranges: 12.1.1 through 12.1.3, or 12.2.3 through 12.2.10.
    Affected if The installed version falls within 12.1.1 to 12.1.3 or 12.2.3 to 12.2.10
  3. Verify Print Server component is enabled
    Check whether the Print Server component of One-to-One Fulfillment is enabled and running. This may be confirmed through the Oracle Applications Manager interface, service configuration, or module status queries.
    Affected if Print Server component is enabled and active
  4. Assess HTTP network exposure
    Determine if the Print Server is accessible via HTTP without authentication. Check network listeners, web server configuration, and firewall rules to see if the Print Server endpoint accepts unauthenticated HTTP connections.
    Affected if Print Server is exposed to HTTP and accepts connections without requiring authentication

You are affected if Oracle One-to-One Fulfillment version 12.1.1-12.1.3 or 12.2.3-12.2.10 is installed with the Print Server component enabled and accessible via unauthenticated HTTP.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.10
Interim mitigation

Apply Oracle Critical Patch Update (CPU) security patches for CVE-2021-2101. If immediate patching is not possible, restrict network access to the One-to-One Fulfillment Print Server via firewall or network segmentation to prevent unauthenticated HTTP access.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.11 or later (patched via CPU)

  1. 1. Log in to Oracle Support and search for the Critical Patch Update (CPU) containing the fix for CVE-2021-2101
  2. 2. Locate the Oracle One-to-One Fulfillment patch for your specific version (12.1.1-12.1.3 or 12.2.3-12.2.10)
  3. 3. Download the appropriate patch from Oracle Support
  4. 4. Review the patch readme and prerequisites documentation
  5. 5. Apply the patch in a test environment first to validate
  6. 6. Schedule a maintenance window and apply the patch to production
  7. 7. Verify the patch was applied successfully and test the Print Server functionality
Caveat Oracle patches are cumulative; apply in non-production first to verify compatibility with customizations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in One To One Fulfillment Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
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,536.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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