dbcve.org
ScriptingApplication · Oracle

CVE-2020-2817

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 Scripting product of Oracle E-Business Suite (component: Miscellaneous). 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 Scripting. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Scripting, 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 Scripting accessible data as well as unauthorized update, insert or delete access to some of Oracle Scripting 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

Oracle Scripting component in Oracle E-Business Suite versions 12.1.1-12.1.3 contains a vulnerability exploitable via HTTP by unauthenticated remote attackers. While requiring human interaction, it allows unauthorized access to critical data and partial data modification (insert/update/delete) capabilities, with high confidentiality and low integrity impacts.

MitigationApply Oracle Critical Patch Update for January 2020 (or subsequent relevant CPU) addressing CVE-2020-2817. Since this is an Oracle E-Business Suite patch requiring downtime and regression testing, plan accordingly.

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
ScriptingApplication
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. Confirm Oracle E-Business Suite installation
    Check if Oracle E-Business Suite is running by querying the database: SELECT release_name FROM fnd_product_groups; or check the context file in $INST_TOP/ora/10.1.2/hostname.xml for the APPL_TOP version.
    Affected if The version returned is 12.1.1, 12.1.2, or 12.1.3.
  2. Verify Oracle Scripting component version
    Query the Oracle Scripting version via SQL: SELECT patch_level FROM ad_patch_drivers WHERE patch_name = 'R12.SCRIPTING'; or check in Oracle Applications Manager (OAM) under Scripting component status.
    Affected if The Scripting component version falls within 12.1.1 to 12.1.3.
  3. Check if Scripting module is accessible via HTTP
    Verify the Oracle Scripting web entry point is exposed. Typically accessible at /OA_HTML/asicmgnt.htm or /OA_HTML/asic_scrpt.htm endpoints. Check your web server configuration (Apache/OHS) for these aliases.
    Affected if The Scripting module URLs are reachable over HTTP/HTTPS without authentication.
  4. Confirm the Oracle Scripting feature is enabled
    Check the Oracle Scripting concurrent manager is configured and enabled. In Oracle EBS, verify through Concurrent > Managers > Scripting Manager is active, or check icx_parameter settings for SCRIPTING_ENABLED = Y.
    Affected if The Scripting feature is enabled and the concurrent manager is running.

A system is affected if Oracle E-Business Suite version 12.1.1 through 12.1.3 is installed, the Oracle Scripting component is enabled, and it is exposed via HTTP without additional authentication controls.

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 Update for January 2020 (or subsequent relevant CPU) addressing CVE-2020-2817. Since this is an Oracle E-Business Suite patch requiring downtime and regression testing, plan accordingly.

Fix this in Scripting Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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