First published: Fri Jan 27 2017(Updated: )
Vulnerability in the Oracle Advanced Outbound Telephony component of Oracle E-Business Suite (subcomponent: User Interface). Supported versions that are affected are 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5 and 12.2.6. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Advanced Outbound Telephony, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Advanced Outbound Telephony accessible data as well as unauthorized update, insert or delete access to some of Oracle Advanced Outbound Telephony accessible data. CVSS v3.0 Base Score 8.2 (Confidentiality and Integrity impacts).
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Advanced Outbound Telephony | =12.1.1 | |
Oracle Advanced Outbound Telephony | =12.1.2 | |
Oracle Advanced Outbound Telephony | =12.1.3 | |
Oracle Advanced Outbound Telephony | =12.2.3 | |
Oracle Advanced Outbound Telephony | =12.2.4 | |
Oracle Advanced Outbound Telephony | =12.2.5 | |
Oracle Advanced Outbound Telephony | =12.2.6 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-3407 has been categorized as easily exploitable and poses a significant risk due to allowing unauthenticated access.
Affected versions of Oracle Advanced Outbound Telephony include 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, and 12.2.6.
To remediate CVE-2017-3407, users should apply the latest security patches provided by Oracle for the affected versions.
CVE-2017-3407 can be exploited by an unauthenticated attacker to gain unauthorized access to sensitive information.
As of the latest information, there are no documented workarounds for CVE-2017-3407, making patching essential for protection.