CVE-2024-21258
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 · uneditedVulnerability in the Oracle Installed Base product of Oracle E-Business Suite (component: User Interface). Supported versions that are affected are 12.2.3-12.2.14. 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 read access to a subset of Oracle Installed Base accessible data. CVSS 3.1 Base Score 5.3 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 confidenceUnauthenticated remote attacker can exploit the User Interface component of Oracle Installed Base (E-Business Suite 12.2.3-12.2.14) via HTTP to gain unauthorized read access to a subset of data. This is an information disclosure vulnerability with network-exploitable low-complexity attacks affecting only confidentiality.
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>= 12.2.3, <= 12.2.14CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle E-Business Suite versionQuery the FND_PRODUCT_INSTALLATIONS table or check the context file (usually in $APPL_TOP/admin/<CONTEXT_NAME>.xml) to determine the EBS version. Run: SELECT release_name FROM fnd_product_groups;Affected if The version is between 12.2.3 and 12.2.14 inclusive
-
Confirm Oracle Installed Base component is presentQuery the Oracle Installed Base tables or check if the IB module is registered in FND_APPLICATION and FND_PRODUCT_INSTALLATIONS. Look for application short name 'IB' or 'CSI' in the installed applications.Affected if The Installed Base module (IB/CS) is installed and registered in the EBS instance
-
Verify HTTP listener is enabled for EBSCheck if the Oracle HTTP Server (OHS) or Apache listener is running and configured for EBS. Inspect the HTTP access logs and configuration for EBS endpoints.Affected if HTTP access to Oracle EBS is enabled and the web listener is active
-
Check network exposure of EBS HTTP interfacesReview firewall rules, load balancer configurations, or network ACLs to determine if the EBS HTTP port (typically 8000-8009) is accessible from untrusted networks.Affected if The EBS HTTP interface is exposed to untrusted or public network segments without proper access restrictions
A user is affected if they run Oracle E-Business Suite versions 12.2.3 through 12.2.14 with the Installed Base module enabled and HTTP interfaces accessible to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply the relevant Oracle Critical Patch Update for this vulnerability. As an interim control, restrict network access to Oracle Installed Base HTTP interfaces to trusted sources only.
- 1. Check the current Oracle E-Business Suite version using the "About Oracle Applications" page in the system administrator responsibility.
- 2. Access Oracle Support and search for the January 2025 Critical Patch Update (CPU) for Oracle E-Business Suite.
- 3. Apply the appropriate security patch for CVE-2024-21258. Oracle typically provides specific patch numbers through their Critical Patch Update advisories.
- 4. Before applying the patch, ensure a full backup of the EBS system and test the patch in a non-production environment.
- 5. Apply the patch using Oracle OPatch or the standard EBS patch application method as documented in the patch readme.
- 6. After patching, verify the patch was successfully applied and restart affected services if required.
- 7. Test the Oracle Installed Base functionality to ensure the patch does not break existing functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21258 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21258 in production — separate from our analysis above.
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.
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.
- 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