Unauthenticated access and modification of interaction data
Published Jan 20, 2021 · Updated Sep 26, 2024
Compromise in Oracle Customer Interaction History 12.1.1 through 12.1.3 and 12.2.3 through 12.2.10 allows remote attackers to read and alter data. Oracle identifies the affected locus only as the Outcome-Result component and has not disclosed the faulty operation on untrusted HTTP input. Exploitation requires no credentials but does require a different person to interact, enabling access to critical or all readable interaction data and limited insertion, update, or deletion of data.
Summary
What happened
Compromise in Oracle Customer Interaction History 12.1.1 through 12.1.3 and 12.2.3 through 12.2.10 allows remote attackers to read and alter data. Oracle identifies the affected locus only as the Outcome-Result component and has not disclosed the faulty operation on untrusted HTTP input. Exploitation requires no credentials but does require a different person to interact, enabling access to critical or all readable interaction data and limited insertion, update, or deletion of data.
The record
- CVE
- CVE-2021-2106
- Published
- Jan 20, 2021
- Updated
- Sep 26, 2024
- Vendor
- Oracle
- Product
- Oracle Customer Interaction History
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 20, 2021CVE publishedPublication date reported by the CVE source.
- Sep 26, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=12.1.1-12.1.3
- Affected versionversion=12.2.3-12.2.10
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo