Installed BaseApplication · Oracle

CVE-2024-20933

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-17

Fix available

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

See remediation →

68/100

Remediation priority · Elevated

Remotely reachable No privileges

Official description

NVD · unedited

Vulnerability in the Oracle Installed Base product of Oracle E-Business Suite (component: Engineering Change Order). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Installed Base. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Installed Base, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Installed Base accessible data as well as unauthorized read access to a subset of Oracle Installed Base accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Technical summary

dbcve analysis · high confidence

Oracle Installed Base Engineering Change Order component contains an HTTP-based vulnerability exploitable by unauthenticated attackers requiring human interaction. The flaw allows unauthorized read and write (update/insert/delete) access to a subset of Oracle Installed Base data, with potential scope expansion to additional products.

MitigationApply Oracle Critical Patch Update (CPU) for January 2024 addressing CVE-2024-20933. As a temporary control, restrict HTTP access to Oracle E-Business Suite interfaces via network segmentation or WAF rules until patching is completed.

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

Installed BaseApplication

Affected:>= 12.2.3, <= 12.2.13

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

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

Am I affected?

dbcve checks

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

Confirm Oracle Installed Base is deployed

Check if Oracle E-Business Suite (EBS) with Installed Base module is running in your environment. Look for Oracle EBS processes or check application inventory for 'Oracle Installed Base' component.

Affected if Oracle Installed Base / Oracle EBS is not present in the environment, the CVE does not apply.
Identify Oracle Installed Base version

Query the Oracle database for the Installed Base version. Use SQL: SELECT VERSION FROM APPS.Oracle_Installed_Base_Version; or check the Oracle E-Business Suite version banner via the login page or FND_GLOBAL.APPS_INITIALIZE. Compare against the affected range: 12.2.3 through 12.2.13.

Affected if Installed version is >= 12.2.3 and <= 12.2.13, the environment is within the affected range.
Determine if Engineering Change Order component is accessible

Verify the Oracle Installed Base Engineering Change Order functionality is enabled. Check Oracle EBS responsibility assignments for 'Installed Base Engineering Change Order' responsibility or equivalent module access control.

Affected if The Engineering Change Order module is available to users via Oracle EBS responsibilities, the attack surface exists.
Check HTTP exposure of Oracle EBS interfaces

Inspect network configuration to determine if Oracle E-Business Suite web interfaces (Oracle Application Server/Oracle HTTP Server) are exposed to untrusted networks. Review load balancer, web server, or WAF configurations for EBS URLs.

Affected if HTTP/HTTPS access to Oracle EBS is reachable from untrusted networks without proper network segmentation, exploitation is possible.

You are affected if Oracle Installed Base version is between 12.2.3 and 12.2.13 inclusive AND the Engineering Change Order web interface is accessible over HTTP from your network perimeter.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.13

Interim mitigation

Apply Oracle Critical Patch Update (CPU) for January 2024 addressing CVE-2024-20933. As a temporary control, restrict HTTP access to Oracle E-Business Suite interfaces via network segmentation or WAF rules until patching is completed.

Recommended fix Moderate confidence

Apply January 2024 Critical Patch Update (CPU) or later CPU

1. Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-20933. For Oracle E-Business Suite, this vulnerability was addressed in the January 2024 CPU.
2. Refer to Oracle Support Document 2943185.1 for the specific patch bundle relevant to Oracle Installed Base.
3. Apply the appropriate Oracle E-Business Suite patch following standard Oracle patching procedures.
4. After patching, verify the CSRF protection is enabled in Oracle Applications Framework (OAF) security settings.
5. Test the Engineering Change Order component to confirm the fix is effective.
6. Review Oracle E-Business Suite security hardening guides to ensure additional CSRF protections are properly configured.

Caveat Standard Oracle CPU patching has minimal risk but should be tested in a non-production environment first due to potential impact on EBS functionality

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Installed Base Scoped from the published advisory

Consultation6.0 h
Implementation12.0 h
Testing10.0 h
Review / QA4.0 h

32.0 hours of engineering $5,580

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2024-20933 — 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-2024-20933 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-20933?

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.13 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Installed Base

Remediation

Need this fixed?

Fix this in Installed Base 32 hrs · Moderate

Typical engagement from $5,580

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-20933 and return a fixed quote.

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