Service BusApplication · Oracle

CVE-2024-21246

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 unauthenticated 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 7.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/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 · moderate confidence

Oracle Service Bus 12.2.1.4.0 contains an unauthenticated HTTP vulnerability in its core functionality that allows remote attackers to access sensitive data without credentials. The attack vector is network-based via HTTP with low complexity, requiring no authentication or user interaction. The vulnerability primarily impacts confidentiality, enabling unauthorized disclosure of data accessible through the OSB.

MitigationApply the Oracle Critical Patch Update that addresses CVE-2024-21246, or upgrade to a patched version of Oracle Service Bus. If immediate patching is not possible, restrict network access to OSB endpoints and implement additional authentication layers.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Log into the WebLogic Administration Console and navigate to the Oracle Service Bus domain, or use WLST command 'ls()' in the domain runtime to check the OSB version. Alternatively, check the Oracle inventory file $ORACLE_HOME/inventory/ContentsXML/oraclehome.xml for the OSB installation version.
    Affected if The installed version is exactly 12.2.1.4.0
  2. Determine if OSB console is network-accessible
    Attempt to access the OSB console URL (typically at /servicebus on the WebLogic managed server port) from a non-localhost network location, or review the network configuration to confirm whether the ListenAddress is set to a non-localhost IP or 0.0.0.0.
    Affected if The OSB console or service endpoints are reachable from network addresses other than localhost/127.0.0.1
  3. Test unauthenticated HTTP access to OSB endpoints
    Send an HTTP GET request to the OSB service endpoint URL without providing any authentication credentials (e.g., using curl or a browser). Common OSB proxy service URLs follow the pattern http://<host>:<port>/<service_path>.
    Affected if HTTP requests to OSB endpoints return successful responses without requiring authentication

You are affected if Oracle Service Bus version 12.2.1.4.0 is installed and its HTTP-based OSB console or service endpoints are accessible over the network without authentication.

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 the Oracle Critical Patch Update that addresses CVE-2024-21246, or upgrade to a patched version of Oracle Service Bus. If immediate patching is not possible, restrict network access to OSB endpoints and implement additional authentication layers.

Fix this in Service Bus 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-21246 — 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-21246 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