dbcve.org
EngineeringApplication · Oracle

CVE-2021-2405

HIGH · 8.1 CVSS v3.1 Published 2021-07-21
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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 Engineering product of Oracle E-Business Suite (component: Change Management). Supported versions that are affected are 12.2.3-12.2.10. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Engineering. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Engineering accessible data as well as unauthorized access to critical data or complete access to all Oracle Engineering accessible data. CVSS 3.1 Base Score 8.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/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

Vulnerability in Oracle E-Business Suite Engineering's Change Management component (versions 12.2.3-12.2.10) allows low-privileged attackers with network access via HTTP to perform unauthorized creation, deletion, or modification of critical data, plus unauthorized access to critical or all accessible data. High confidentiality and integrity impact with no availability impact.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2021-2405. Until patched, restrict network access to Oracle Engineering HTTP endpoints and monitor for unauthorized change management activity.

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
EngineeringApplication
Affected:>= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm Oracle E-Business Suite installation
    Query the database or application tier for the presence of Oracle E-Business Suite. Check for Oracle Engineering modules via Oracle Applications Manager (OAM) or by querying the FND_PRODUCT_INSTALLATIONS table.
    Affected if Oracle E-Business Suite is not installed, this CVE does not apply.
  2. Identify Oracle Engineering version
    Log into Oracle Applications Manager or use the adident utility (adident Header $ENGINEERING_TOP/patch/115/import/engchgpc.pls) to determine the exact version of the Oracle Engineering Change Management component.
    Affected if The installed version falls within 12.2.3 through 12.2.10 inclusive.
  3. Verify HTTP access is enabled
    Check the Oracle E-Business Suite HTTP server configuration (context file in $INST_TOP/Applications/oacore) and confirm whether the Oracle Engineering Change Management servlets and JSPs are accessible via HTTP listeners. Use OAM to inspect the module's enabled protocols.
    Affected if HTTP or HTTPS access is enabled for the Change Management module; this is required for the network-based attack vector.
  4. Assess network exposure
    Review firewall rules, WebLogic/Oracle HTTP Server configurations, and load balancer settings to determine if the Oracle Engineering HTTP endpoints are exposed to untrusted networks. Check for direct internet-facing access to /engchg* or /Engineering paths.
    Affected if The Change Management HTTP endpoints are reachable from untrusted networks without proper access controls.
  5. Review access logs for unauthorized change management activity
    Examine Oracle E-Business Suite audit logs, Apache access logs, and Oracle Fusion Middleware logs for suspicious POST/GET requests to Change Management endpoints (such as engchg*, change management servlets) from unexpected users or IP addresses.
    Affected if Evidence exists of unauthorized creation, modification, or deletion operations in change management logs.

You are affected if Oracle E-Business Suite with Oracle Engineering is installed and the version is between 12.2.3 and 12.2.10 with HTTP access enabled to the Change Management component.

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

Apply Oracle Critical Patch Update (CPU) containing the fix for CVE-2021-2405. Until patched, restrict network access to Oracle Engineering HTTP endpoints and monitor for unauthorized change management activity.

Fix this in Engineering 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-2405 — 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-2405 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