CVE-2024-21276
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 Work in Process product of Oracle E-Business Suite (component: Messages). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Work in Process. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Work in Process accessible data as well as unauthorized access to critical data or complete access to all Oracle Work in Process 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 confidenceOracle Work in Process Messages component contains a vulnerability allowing low-privileged attackers with network access via HTTP to perform unauthorized creation, deletion, modification, and read access to critical data within the affected module.
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.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Oracle E-Business Suite is installedCheck for Oracle E-Business Suite installation directories or running services. Common paths include $ORACLE_HOME/apps or look for Oracle HTTP Server processes listening on ports like 8000-8001. Use 'ps -ef | grep -i oracle' or check for Oracle-related services.Affected if Oracle E-Business Suite is not found in the environment, the system is not affected.
-
Determine Oracle E-Business Suite versionQuery the database using SQL: SELECT version FROM fnd_product_groups WHERE product_group_id = 1; OR check the context file in $INST_TOP/appl/admin/<context_name>.ctx for the version string. The version typically appears as '12.2.x'.Affected if The installed version falls within the range >= 12.2.3 and <= 12.2.13, the system may be affected.
-
Verify Work in Process module is accessibleCheck if the WIP (Work in Process) module is enabled and accessible via Oracle Application Manager (OAM) or through the web interface at /OA_HTML/wip/ or check via SQL: SELECT enabled_flag FROM fnd_application WHERE application_id IN (SELECT application_id FROM fnd_application_tl WHERE application_name LIKE 'Work in Process%');Affected if The WIP module is enabled and accessible over HTTP, the vulnerability can be exploited.
-
Check network accessibility to Oracle EBS HTTP servicesVerify that the Oracle E-Business Suite web tier is exposed to the network. Check firewall rules and listener configuration in $ORACLE_HOME/ listener.ora. Use 'netstat -an | grep -E "(8000|8001|4444)"' to identify exposed HTTP ports.Affected if The Oracle EBS HTTP ports are reachable from untrusted networks, low-privileged attackers can exploit the vulnerability remotely.
The environment is affected if Oracle E-Business Suite version 12.2.3 through 12.2.13 is installed, the Work in Process module is enabled, and the HTTP interface is network-accessible to low-privileged attackers.
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 Oracle Critical Patch Update addressing CVE-2024-21276 to Oracle E-Business Suite 12.2.3-12.2.13, or implement compensating controls such as web application firewall rules and network access restrictions until patching can be completed.
- 1. Subscribe to Oracle Critical Patch Updates to receive the security patch for CVE-2024-21276
- 2. Apply the relevant Oracle E-Business Suite Security Patch from the Critical Patch Update that addresses this vulnerability
- 3. Alternatively, contact Oracle Support for the specific patch number (PID) for this CVE in the Work in Process Messages component
- 4. After applying the patch, verify the fix by testing the Messages functionality in Oracle Work in Process
- 5. Confirm the patch was applied successfully by checking the AD applied patches in Oracle Applications Manager
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.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 $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21276 — 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-21276 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