ScriptingApplication · Oracle

CVE-2021-2091

HIGH · 8.2 CVSS v3.1 Published 2021-01-20

Fix available

A fix is available. Upgrade to after 12.2.10 or later.

See remediation →

89/100

Remediation priority · High

Remotely reachable No privileges

Official description

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 and 12.2.3-12.2.10. 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.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

dbcve analysis · high confidence

Vulnerability in Oracle E-Business Suite Oracle Scripting component (Miscellaneous category) affecting versions 12.1.1-12.1.3 and 12.2.3-12.2.10. Unauthenticated remote attacker with network access via HTTP can exploit this flaw, which requires human interaction to trigger. The vulnerability allows unauthorized access to critical data or complete access to all Oracle Scripting accessible data, plus unauthorized update/insert/delete operations on some accessible data.

MitigationApply Oracle Critical Patch Updates for the affected Oracle E-Business Suite versions. If immediate patching is not feasible, restrict network access to Oracle Scripting interfaces via firewall or access controls until the patch can be deployed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

ScriptingApplication

Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify Oracle E-Business Suite installation

Check for Oracle E-Business Suite installation by looking for Oracle application directories (commonly $ORACLE_HOME/apps or similar paths) and querying the database for APPS schema version information using SQL: SELECT release_name FROM apps.fnd_product_groups;

Affected if The installed version falls within 12.1.1 to 12.2.10 (specifically 12.1.1-12.1.3 or 12.2.3-12.2.10)
Check Oracle Scripting component version

Query the Oracle Scripting component version through the Oracle Application Manager interface or by checking the icx_launch.jsp and scripting-related JAR files in the $OA_HTML directory. Use SQL: SELECT patch_level FROM ad_patch_drivers WHERE patch_name LIKE '%SCRIPTING%';

Affected if The Oracle Scripting component version is between 12.1.1 and 12.2.10 inclusive
Verify Oracle Scripting HTTP endpoints are exposed

Check if the Oracle Scripting servlet endpoints are accessible by attempting to access common paths such as /OA_HTML/icx_launch.jsp or /OA_HTML/oracle/sc/ through a web browser or curl command from an internal network location

Affected if The Oracle Scripting HTTP endpoints are reachable over the network without requiring authentication
Confirm network accessibility

Review firewall rules, load balancer configurations, or WebGate/OHS settings to determine if the Oracle Scripting URLs are exposed to untrusted networks. Check listener.ora and httpd.conf for any ProxyPass directives exposing /OA_HTML/

Affected if The Oracle Scripting interface is exposed to network access beyond trusted internal networks, especially the internet
Check for existing access controls

Examine Oracle E-Business Suite function security settings (via Functional Administrator responsibility) and ICX table permissions to verify if unauthenticated or low-privilege users can access Oracle Scripting functions

Affected if Anonymous or guest user accounts can access Oracle Scripting functionality without proper authentication or authorization checks
Review recent access logs

Examine Apache/OHS access logs (in $ORACLE_HOME/Apache/logs) and Oracle E-Business Suite ICX logs for unusual or unauthorized access patterns to Oracle Scripting URLs, particularly POST requests to scripting endpoints

Affected if There are unauthorized requests to Oracle Scripting endpoints from untrusted IP addresses or unexpected user agents

You are affected if Oracle E-Business Suite with Oracle Scripting component versions 12.1.1-12.1.3 or 12.2.3-12.2.10 is installed and the Oracle Scripting HTTP interface is network-accessible, especially from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 12.2.10

Interim mitigation

Apply Oracle Critical Patch Updates for the affected Oracle E-Business Suite versions. If immediate patching is not feasible, restrict network access to Oracle Scripting interfaces via firewall or access controls until the patch can be deployed.

Fix this in Scripting 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 the upgrade done

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-2021-2091 — 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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-2091 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2021-2091?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 12.2.10 or later

Severity 8.2 High

Exploit likelihood EPSS, next 30 days 1.2%

Affects: Scripting

Remediation

A high-priority fix

Fix this in Scripting 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2021-2091 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References