8.2
Advisory Published
Updated

CVE-2017-3430

First published: Fri Jan 27 2017(Updated: )

Vulnerability in the Oracle One-to-One Fulfillment 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 One-to-One Fulfillment. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle One-to-One Fulfillment, 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 One-to-One Fulfillment accessible data as well as unauthorized update, insert or delete access to some of Oracle One-to-One Fulfillment accessible data. CVSS v3.0 Base Score 8.2 (Confidentiality and Integrity impacts).

Credit: secalert_us@oracle.com

Affected SoftwareAffected VersionHow to fix
Oracle One-to-One Fulfillment=12.1.1
Oracle One-to-One Fulfillment=12.1.2
Oracle One-to-One Fulfillment=12.1.3
Oracle One-to-One Fulfillment=12.2.3
Oracle One-to-One Fulfillment=12.2.4
Oracle One-to-One Fulfillment=12.2.5
Oracle One-to-One Fulfillment=12.2.6

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2017-3430?

    CVE-2017-3430 is considered a critical vulnerability due to its ability to be easily exploited by unauthenticated attackers.

  • How do I fix CVE-2017-3430?

    To fix CVE-2017-3430, you should apply the latest patches provided by Oracle for the affected versions of Oracle One-to-One Fulfillment.

  • Which versions of Oracle One-to-One Fulfillment are affected by CVE-2017-3430?

    CVE-2017-3430 affects Oracle One-to-One Fulfillment versions 12.1.1, 12.1.2, 12.1.3, 12.2.3, 12.2.4, 12.2.5, and 12.2.6.

  • What type of attackers can exploit CVE-2017-3430?

    CVE-2017-3430 can be exploited by unauthenticated attackers, making it particularly concerning for organizations.

  • Is there a workaround for CVE-2017-3430 while I wait for a patch?

    No official workaround is available for CVE-2017-3430, so it is crucial to apply patches as soon as they are available.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203