Fusion MiddlewareApplication · Oracle

CVE-2024-21205

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 Service Bus product of Oracle Fusion Middleware (component: OSB Core Functionality). The supported version that is affected is 12.2.1.4.0. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Service Bus. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Service Bus accessible data. CVSS 3.1 Base Score 6.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 confidence

This is an information disclosure vulnerability in Oracle Service Bus 12.2.1.4.0 affecting the OSB Core Functionality component. The CVSS vector indicates a network-exploitable issue requiring low privilege authentication that results in high confidentiality impact - allowing unauthorized access to sensitive data accessible through the Service Bus without affecting integrity or availability.

MitigationApply Oracle's security patch for CVE-2024-21205 to the Oracle Service Bus 12.2.1.4.0 deployment. Review access controls and authentication configurations around OSB core functionality as a compensating control until the patch can be applied.

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
Fusion MiddlewareApplication
Affected:= 12.2.1.4.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Identify Oracle Service Bus installation version
    Run the Oracle OPatch lsinventory command or check the OSB installation directory for the version. In the Oracle Home directory, check the README or inventory files for the exact version number.
    Affected if The installed version is exactly 12.2.1.4.0
  2. Verify OSB Core Functionality is deployed
    Access the Oracle Enterprise Manager Fusion Middleware Control console and navigate to the Service Bus domain to confirm OSB core components are active, or check the OSB domain configuration files in the config directory.
    Affected if OSB Core Functionality is deployed and running on version 12.2.1.4.0
  3. Review OSB service access control policies
    Use the Oracle Enterprise Manager console or WLST commands to list the access control policies configured for proxy services and business services in the OSB domain.
    Affected if Low-privilege or unauthenticated users can access sensitive OSB proxy or business service endpoints
  4. Inspect OSB transportation and security configuration
    Check the OSB service configuration files (sbconfig.xml) or the Service Bus console for transportation settings, particularly for publicly accessible proxy service endpoints.
    Affected if Proxy services are configured without proper authentication or with overly permissive access controls

You are affected if Oracle Service Bus version 12.2.1.4.0 is deployed with OSB Core Functionality and the service endpoints allow unauthorized or low-privilege access to sensitive data.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle's security patch for CVE-2024-21205 to the Oracle Service Bus 12.2.1.4.0 deployment. Review access controls and authentication configurations around OSB core functionality as a compensating control until the patch can be applied.

Fix this in Fusion Middleware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21205 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21205 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