First published: Mon Apr 24 2017(Updated: )
Vulnerability in the Oracle Retail Open Commerce Platform component of Oracle Retail Applications (subcomponent: Web). Supported versions that are affected are 4.0, 5.0, 5.1, 5.3, 6.0,6.1, 15.0 and 16.0. Easily "exploitable" vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Retail Open Commerce Platform. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Retail Open Commerce Platform, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Retail Open Commerce Platform accessible data as well as unauthorized read access to a subset of Oracle Retail Open Commerce Platform 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).
Credit: secalert_us@oracle.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Retail Open Commerce Platform | =4.0 | |
Oracle Retail Open Commerce Platform | =5.0 | |
Oracle Retail Open Commerce Platform | =5.1 | |
Oracle Retail Open Commerce Platform | =5.3 | |
Oracle Retail Open Commerce Platform | =6.0 | |
Oracle Retail Open Commerce Platform | =6.1 | |
Oracle Retail Open Commerce Platform | =15.0 | |
Oracle Retail Open Commerce Platform | =16.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-3451 is considered an easily exploitable vulnerability that allows a low privileged attacker network access.
To fix CVE-2017-3451, it is recommended to apply the latest patches and updates provided by Oracle for the affected versions.
CVE-2017-3451 affects versions 4.0, 5.0, 5.1, 5.3, 6.0, 6.1, 15.0, and 16.0 of Oracle Retail Open Commerce Platform.
An attacker needs low privileged network access via HTTP to exploit CVE-2017-3451.
There are no officially documented workarounds for CVE-2017-3451, so applying patches is strongly advised.