dbcve.org
ScriptingApplication · Oracle

CVE-2021-2029

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to after 12.2.8 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 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.8. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Scripting. Successful attacks of this vulnerability can result in takeover of Oracle Scripting. CVSS 3.1 Base Score 9.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

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

This is a critical vulnerability in Oracle Scripting (part of Oracle E-Business Suite) that allows unauthenticated remote attackers to achieve complete system compromise via HTTP network access. The vulnerability affects versions 12.1.1-12.1.3 and 12.2.3-12.2.8, enabling full takeover impacting confidentiality, integrity, and availability.

MitigationApply the relevant Oracle Critical Patch Update (CPU) that addresses CVE-2021-2029. If patching is immediately infeasible, restrict network access to Oracle Scripting interfaces via firewall or web application firewall until the patch can be applied.

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>= 12.2.3, <= 12.2.8

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 if Oracle E-Business Suite with Oracle Scripting is deployed
    Check your Oracle installation inventory or look for Oracle Scripting components in your application server. Oracle Scripting is part of the Oracle E-Business Suite. Consult your system documentation or Oracle application inventory.
    Affected if Oracle Scripting is not present in your environment, you are not affected.
  2. Determine the installed Oracle Scripting version
    Use Oracle Application Manager or query the Oracle database for the Oracle Scripting version. The version is typically available in the Oracle E-Business Suite version information screen (Home > About Oracle Application).
    Affected if You cannot determine the version - you cannot confirm you are not affected.
  3. Compare your version against affected ranges
    Check if your Oracle Scripting version falls within >= 12.1.1 to <= 12.1.3 OR >= 12.2.3 to <= 12.2.8. These are the vulnerable version ranges.
    Affected if Your installed version matches either 12.1.1-12.1.3 or 12.2.3-12.2.8, you are running a vulnerable version.
  4. Verify if Oracle Scripting HTTP interfaces are network accessible
    Determine if Oracle Scripting web endpoints are exposed to network access. Check firewall rules, load balancer configurations, or web server settings that control access to Oracle Scripting URLs (typically under /OA_HTML/ or /scripting/ paths).
    Affected if Oracle Scripting HTTP interfaces are directly accessible from untrusted networks, the vulnerability can be exploited remotely.
  5. Check for compensating network controls
    Review network segmentation, firewall rules, or WAF configurations that may restrict access to Oracle Scripting interfaces. Verify if access is limited to trusted networks or requires authentication at the network layer.
    Affected if No network restrictions exist and you run a vulnerable version, you are at high risk from unauthenticated remote attacks.

You are affected if Oracle Scripting is installed and your version falls within 12.1.1-12.1.3 or 12.2.3-12.2.8, especially if the HTTP interface is network-accessible without restrictions.

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.2.8
Interim mitigation

Apply the relevant Oracle Critical Patch Update (CPU) that addresses CVE-2021-2029. If patching is immediately infeasible, restrict network access to Oracle Scripting interfaces via firewall or web application firewall until the patch can be applied.

Fix this in Scripting Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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