CVE-2023-21849
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 Applications DBA product of Oracle E-Business Suite (component: Java utils). Supported versions that are affected are 12.2.3-12.2.12. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Applications DBA. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Applications DBA accessible data. CVSS 3.1 Base Score 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 · moderate confidenceUnauthenticated HTTP vulnerability in Oracle E-Business Suite Applications DBA Java utils component (versions 12.2.3-12.2.12) allows remote attackers to create, delete or modify critical data without credentials via network access.
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.12CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 Oracle E-Business Suite installationCheck for Oracle E-Business Suite by reviewing environment variables (ORACLE_HOME, $APPS_CONTEXT), or look for Oracle-specific directory structures such as $APPL_TOP, $ORACLE_HOME, or the presence of Oracle E-Business Suite configuration files in the system.Affected if Oracle E-Business Suite is present on the server.
-
Determine the exact EBS versionQuery the Oracle Applications version using SQL*Plus connected as APPS user: SELECT release_name FROM fnd_product_groups; or check the context file (typically located in $APPL_TOP/admin/<context_name>.xml) for the release version.Affected if The version falls within 12.2.3 through 12.2.12 inclusive.
-
Verify the DBA Java utils component is accessibleCheck if the DBA Java utils are exposed via HTTP/HTTPS by attempting to access the URL path /oa_servlets/oracle.apps.fnd.diagnostics.Diag or reviewing web tier configuration files (like mod_plsql configuration) for servlet mappings related to DBA utilities.Affected if The DBA Java utils servlet is mapped and accessible through the web listener.
-
Confirm HTTP/HTTPS listener exposureReview the web tier configuration (HTTP Server httpd.conf, Oracle Web Listener settings) or test network connectivity to the Oracle E-Business Suite ports (typically 8000, 8080, or 443) from untrusted networks to determine if the application is externally accessible.Affected if The Oracle E-Business Suite HTTP/HTTPS ports are reachable from untrusted or public networks without proper network filtering.
A user is affected if Oracle E-Business Suite version 12.2.3-12.2.12 is installed, the DBA Java utils component is exposed via HTTP/HTTPS, and the interface is accessible from 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 Oracle Critical Patch Update (CPU) for January 2023 or subsequent relevant security patches. Restrict HTTP/HTTPS access to Oracle Applications DBA interfaces to trusted networks if immediate patching is not feasible.
Upgrade to a version beyond 12.2.12 (e.g., 12.2.13 or latest 12.2.x stable release) that includes the CVE-2023-21849 fix
- 1. Review Oracle Critical Patch Update advisories for CVE-2023-21849 on oracle.com for the specific patch bundle applicable to your Oracle E-Business Suite version.
- 2. Identify your current Oracle Applications DBA Java utils component version via Oracle E-Business Suite administration utilities.
- 3. Apply the relevant Oracle Critical Patch Update that addresses CVE-2023-21849, following Oracle's standard patching procedures for E-Business Suite.
- 4. After patching, verify the Oracle Applications DBA component has been updated and test functionality to ensure the fix was applied correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing12.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,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21849 — 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-2023-21849 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