CVE-2024-20950VulnerabilityPublished 16 Jan 2024Updated 2 Jun 2025

CVE-2024-20950: Oracle Customer Interaction History · Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to

Affects Oracle Customer Interaction HistorySource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavencom.oracle/customer-interaction-history`pkg:maven/com.oracle/customer-interaction-history`Other threats	Affected =12.2.3	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement targeted mitigations beyond generic advice: 1) Conduct immediate inventory and version assessment of Oracle Customer Interaction History deployments to identify affected versions (12.2.3 to 12.2.13). 2) Monitor Oracle security advisories closely for official patches or workarounds and apply them promptly once available. 3) Implement strict network segmentation and firewall rules to restrict HTTP access to Oracle E-Business Suite components, limiting exposure to untrusted networks. 4) Enhance user awareness training focused on phishing and social engineering to reduce the likelihood of successful user interaction exploitation. 5) Deploy web application firewalls (WAF) with custom rules to detect and block suspicious HTTP requests targeting Oracle Customer Interaction History endpoints. 6) Enable detailed logging and monitoring of database operations related to Customer Interaction History to detect unauthorized read or write activities. 7) Review and tighten access controls and permissions within Oracle E-Business Suite to minimize data exposure and limit the impact of potential exploits. 8) Consider implementing multi-factor authentication (MFA) for users accessing Oracle systems to add an additional security layer, even though the vulnerability does not require authentication. 9) Prepare incident response plans specifically addressing potential data integrity and confidentiality breaches stemming from this vulnerability.

Description

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).

Impact

For European organizations, the impact of CVE-2024-20950 can be significant, especially for those relying on Oracle E-Business Suite Customer Interaction History for managing customer data and interactions. Unauthorized read access could expose sensitive customer information, leading to privacy violations under GDPR and potential regulatory penalties. Unauthorized modification of data could corrupt customer records, disrupt business processes, and degrade service quality. The scope change implies that integrated Oracle products could also be compromised, amplifying the risk across enterprise systems. Given the requirement for user interaction, phishing or social engineering campaigns targeting European employees could be a vector, increasing the risk of successful exploitation. The medium severity rating suggests a moderate but tangible threat that could affect confidentiality and integrity without causing system downtime. Organizations in sectors such as finance, telecommunications, retail, and public services that heavily use Oracle E-Business Suite are particularly at risk, as compromised customer data could lead to financial fraud, reputational damage, and operational disruptions.

References

oracle.com/security-alerts/cpujan2024.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Jul 2025, 16:42 UTC

Technical details

References

Community reviews

Related threats