dbcve.org
Customer Interaction HistoryApplication · Oracle

CVE-2024-20951

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-17
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Customer Interaction History product of Oracle E-Business Suite (component: Outcome-Result). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Customer Interaction History. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Customer Interaction History, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Customer Interaction History accessible data as well as unauthorized read access to a subset of Oracle Customer Interaction History accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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

Unauthenticated HTTP vulnerability in Oracle Customer Interaction History's Outcome-Result component allows unauthorized read and write access to data through requests that require human interaction (likely CSRF or similar), with potential scope change to affect additional products.

MitigationApply Oracle Critical Patch Update for January 2024 (or subsequent) to address CVE-2024-20951; verify the Outcome-Result component is not exposed to untrusted networks.

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
Customer Interaction HistoryApplication
Affected:>= 12.2.3, <= 12.2.13

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Customer Interaction History installation
    Locate Oracle Customer Interaction History (CHI) in your environment by checking Oracle Application Server, Oracle WebLogic domains, or Oracle Fusion Middleware inventory files (e.g., oraInventory/ContentsXML/inventory.xml, or Oracle Fusion Middleware inventory)
    Affected if Oracle Customer Interaction History version falls within 12.2.3 through 12.2.13 inclusive
  2. Determine installed version of Oracle Customer Interaction History
    Query the Oracle Fusion Middleware version using Oracle Enterprise Manager, opmnctl status, or check the Oracle CHI version file in the Oracle home directory (typically found in $ORACLE_HOME/oraInst.loc or version.txt)
    Affected if Reported version is between 12.2.3 and 12.2.13 inclusive (note: version comparison should account for patch levels)
  3. Verify the Outcome-Result component is enabled and accessible
    Check if the Outcome-Result web component is deployed and accessible by attempting to access the component URL path (typically under /cia/ or /chi/ web contexts) or by examining the Oracle WebLogic deployment descriptors and application configuration
    Affected if Outcome-Result component is deployed and responds to HTTP requests
  4. Check network exposure of the Outcome-Result interface
    Examine the WebLogic console or Oracle HTTP Server configuration to determine if the Outcome-Result endpoint is exposed to untrusted networks (check listener configuration, virtual host settings, and firewall rules for the web tier hosting the application)
    Affected if The HTTP endpoint for Outcome-Result is reachable from untrusted/internal networks without proper authentication enforcement

Your environment is affected if Oracle Customer Interaction History version 12.2.3 through 12.2.13 is installed AND the Outcome-Result component is deployed and exposed via HTTP to your network.

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
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply Oracle Critical Patch Update for January 2024 (or subsequent) to address CVE-2024-20951; verify the Outcome-Result component is not exposed to untrusted networks.

Fix this in Customer Interaction History 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 the upgrade done

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-20951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-20951 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