CVE-2019-2857
CVE-2019-2857 is a medium-severity vulnerability in Oracle Siebel Ui Framework with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.
Key facts
- Severity: Medium (CVSS 3.x base score 5.4)
- CVSS v2: 4.9
- EPSS exploit prediction: 1% (50th percentile)
- Actively exploited: Not listed in CISA KEV
- Affected product: Oracle Siebel Ui Framework
- Published:
- Last modified:
Description
Vulnerability in the Siebel UI Framework component of Oracle Siebel CRM (subcomponent: UIF Open UI). Supported versions that are affected are 19.0 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Siebel UI Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Siebel UI Framework, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Siebel UI Framework accessible data as well as unauthorized read access to a subset of Siebel UI Framework accessible data. CVSS 3.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
Frequently asked questions
- What is CVE-2019-2857?
- Vulnerability in the Siebel UI Framework component of Oracle Siebel CRM (subcomponent: UIF Open UI). Supported versions that are affected are 19.0 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Siebel UI Framework. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Siebel UI Framework, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Siebel UI Framework accessible data as well as unauthorized read access to a subset of Siebel UI Framework accessible data. CVSS 3.0 Base Score 5.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N).
- How severe is CVE-2019-2857?
- CVE-2019-2857 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and user interaction. Impact on confidentiality is low, integrity low, and availability none.
- Is CVE-2019-2857 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (50th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-2857?
- CVE-2019-2857 affects Oracle Siebel Ui Framework. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2019-2857?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2019-2857 published?
- CVE-2019-2857 was published on 2019-07-23 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:oracle:siebel_ui_framework:*:*:*:*:*:*:*:*
More vulnerabilities in Oracle Siebel Ui Framework
- CVE-2020-1938 — Critical (CVSS 9.8): When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat.…
- CVE-2019-20330 — Critical (CVSS 9.8): FasterXML jackson-databind 2.x before 2.9.10.2 lacks certain net.sf.ehcache blocking.
- CVE-2019-16942 — Critical (CVSS 9.8): A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is…
- CVE-2019-14379 — Critical (CVSS 9.8): SubTypeValidator.java in FasterXML jackson-databind before 2.9.9.2 mishandles default typing when ehcache is used…
- CVE-2018-14718 — Critical (CVSS 9.8): FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to execute arbitrary code by leveraging…
- CVE-2017-5645 — Critical (CVSS 9.8): In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log…