Customer Interaction HistoryApplication · Oracle

CVE-2024-20949

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

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

dbcve analysis · high confidence

Unauthenticated HTTP vulnerability in Oracle Customer Interaction History's Outcome-Result component allows remote attackers to read and modify a subset of accessible data. Exploitation requires human interaction (UI:R) and results in low confidentiality and integrity impacts with scope change affecting additional products.

MitigationApply Oracle's Critical Patch Update (CPU) for January 2024 or later that addresses CVE-2024-20949 to Oracle E-Business Suite versions 12.2.3-12.2.13.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Customer Interaction HistoryApplication

Affected:>= 12.2.3, <= 12.2.13

CVSS breakdown

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?

dbcve checks

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

Identify Oracle E-Business Suite installation

Query the database for the installed E-Business Suite version using: SELECT release_name FROM apps.fnd_product_groups; or check the E-Business Suite homepage footer for the version number.

Affected if The version is not between 12.2.3 and 12.2.13 (inclusive), then the system is not vulnerable to this specific CVE.
Verify Customer Interaction History module version

Check if Oracle Customer Interaction History is installed by querying: SELECT application_name, version FROM apps.fnd_application_vl WHERE application_name LIKE '%Customer Interaction History%';

Affected if The module is present and its version falls within 12.2.3 to 12.2.13.
Confirm Outcome-Result component status

Query the Oracle Applications Manager (OAM) or use FND_CONCURRENT_REQUESTS to check if the Outcome-Result functionality is configured and accessible. Check ICX_POR_REPORT_PKG or related concurrent programs.

Affected if The Outcome-Result component is enabled and accessible via HTTP without authentication.
Check HTTP access to the vulnerable endpoint

Review the Oracle E-Business Suite web tier configuration and URL access patterns. Look for unauthenticated access to /OA_HTML/xx (where xx represents custom forms or the Outcome-Result servlet). Examine Oracle HTTP Server (OHS) configuration files for exposed endpoints.

Affected if The Outcome-Result servlet is accessible over HTTP without requiring login credentials.

A system is affected if Oracle Customer Interaction History version 12.2.3 through 12.2.13 is installed with the Outcome-Result component accessible via unauthenticated HTTP.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 12.2.13

Interim mitigation

Apply Oracle's Critical Patch Update (CPU) for January 2024 or later that addresses CVE-2024-20949 to Oracle E-Business Suite versions 12.2.3-12.2.13.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later

1. Review the Oracle Critical Patch Update advisory for January 2024 (or the applicable CPU that addressed CVE-2024-20949)
2. Obtain the required Oracle E-Business Suite patches from Oracle Support (support.oracle.com)
3. Apply the security patch for the Customer Interaction History component (Outcome-Result)
4. After applying the patch, verify the fix by checking the Oracle E-Business Suite version information
5. Test the Oracle Customer Interaction History functionality to confirm the patch does not negatively impact existing operations
6. Restart any Oracle E-Business Suite services as required by the patch documentation

Caveat Review Oracle's patch prerequisites and patch combination requirements before applying; some patches may require specific interim patches first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Customer Interaction History Scoped from the published advisory

Consultation3.0 h
Implementation6.0 h
Testing4.0 h
Review / QA2.0 h

15.0 hours of engineering $2,640

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20949 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2024-20949?

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.

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

At a glance

A fix existsUpgrade to after 12.2.13 or later

Severity 6.1 Medium

Exploit likelihood EPSS, next 30 days 0.4%

Affects: Customer Interaction History

Remediation

Need this fixed?

Fix this in Customer Interaction History 15 hrs · Moderate

Typical engagement from $2,640

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2024-20949 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References