dbcve.org
Installed BaseApplication · Oracle

CVE-2022-21251

HIGH · 7.5 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 12.2.11 or later.
See remediation →
84/100
Remediation priority · High
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 Installed Base product of Oracle E-Business Suite (component: Instance Main). Supported versions that are affected are 12.2.3-12.2.11. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Installed Base. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Installed Base. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 · high confidence

CVE-2022-21251 is a denial-of-service vulnerability in the Oracle Installed Base module of Oracle E-Business Suite (versions 12.2.3-12.2.11). The flaw is exploitable remotely by unauthenticated attackers via HTTP, allowing them to crash or hang the Installed Base component, resulting in availability loss.

MitigationApply the applicable Oracle Critical Patch Update (CPU) for this vulnerability. Prior to production deployment, test the patch in a non-production EBS environment given the module's integration with other EBS components.

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
Installed BaseApplication
Affected:>= 12.2.3, <= 12.2.11

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm Oracle E-Business Suite installation
    Identify if the target system is running Oracle E-Business Suite by checking for Oracle EBS-specific processes, services, or web application fingerprints. Look for Oracle application server processes or EBS-specific URLs/endpoints.
    Affected if The system is running Oracle E-Business Suite and the Installed Base module is deployed and accessible.
  2. Verify EBS version falls within affected range
    Check the installed Oracle E-Business Suite version. In an Oracle EBS environment, this can typically be obtained from the About Oracle Applications page, context file, or by querying the FND_PRODUCT_GROUPS or similar Oracle EBS version tables.
    Affected if The installed version is greater than or equal to 12.2.3 and less than or equal to 12.2.11.
  3. Confirm Installed Base module is enabled
    Determine if the Oracle Installed Base (IB) module is enabled and accessible. Check the module's availability through Oracle EBS module configuration or by attempting to access the module's URL endpoint if known in your environment.
    Affected if The Installed Base module is enabled and exposed within the EBS environment.
  4. Check HTTP accessibility of the module
    Verify that the Installed Base module is accessible via HTTP/HTTPS network access. This may involve checking network exposure, firewall rules, or testing connectivity to the module's web endpoint.
    Affected if The Installed Base module is reachable over the network via HTTP protocol, making it exploitable remotely.

A user is affected if they are running Oracle E-Business Suite version 12.2.3 through 12.2.11 with the Installed Base module enabled and accessible via HTTP, as this allows unauthenticated remote attackers to cause denial of service.

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

Apply the applicable Oracle Critical Patch Update (CPU) for this vulnerability. Prior to production deployment, test the patch in a non-production EBS environment given the module's integration with other EBS components.

Fix this in Installed Base Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing20.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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