dbcve.org
One To One FulfillmentApplication · Oracle

CVE-2017-3557

HIGH · 7.1 CVSS v3.0 Published 2017-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/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 component of Oracle E-Business Suite (subcomponent: Print Server). Supported versions that are affected are 12.1.3, 12.2.3, 12.2.4, 12.2.5 and 12.2.6. 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 · moderate confidence

Unauthenticated HTTP vulnerability in Oracle E-Business Suite's One-to-One Fulfillment Print Server component allows remote attackers to gain unauthorized access to critical data and perform unauthorized updates/inserts/deletes. Exploitation requires human interaction and the scope may extend to additional products beyond the vulnerable component.

MitigationApply Oracle Critical Patch Update addressing CVE-2017-3557; until patch is available, restrict network access to the Print Server interface and implement additional authentication controls.

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= 12.2.3= 12.2.4= 12.2.5= 12.2.6

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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 E-Business Suite version
    Query the database using: SELECT release_name FROM apps.fnd_product_groups; or check the $APPL_TOP/ADMIN directory for the version.txt file.
    Affected if The version matches 12.1.3, 12.2.3, 12.2.4, 12.2.5, or 12.2.6 exactly.
  2. Confirm One-to-One Fulfillment component is installed
    Check if the Oracle One-to-One Fulfillment module is present by querying: SELECT application_name FROM apps.fnd_application WHERE application_name LIKE '%Fulfillment%'; or check the $FND_TOP directory exists.
    Affected if The One-to-One Fulfillment application component is found in the installation.
  3. Verify Print Server functionality is enabled
    Check the Print Server configuration in the Oracle Applications Manager (OAM) console or inspect the FND_OA_CONTEXT file for print server settings at $APPL_TOP/admin/<CONTEXT_NAME>.xml.
    Affected if The Print Server (IBY_FNDSP) is enabled in the application context configuration.
  4. Determine if HTTP access to Print Server is exposed
    Review the Oracle HTTP Server configuration (httpd.conf or oracle_apache.conf) and check if the /OA_HTML/ibyf/ or /printServer/ paths are accessible, or test with: curl -I http://<host>/OA_HTML/ibyf/fg/ExecutePaymentPrint.
    Affected if The Print Server HTTP endpoints are accessible without requiring authentication.

A user is affected if they run Oracle E-Business Suite versions 12.1.3, 12.2.3, 12.2.4, 12.2.5, or 12.2.6 AND have the One-to-One Fulfillment Print Server component enabled with unauthenticated HTTP access exposed.

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 addressing CVE-2017-3557; until patch is available, restrict network access to the Print Server interface and implement additional authentication controls.

Fix this in One To One Fulfillment Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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