In addition, it is possible to conduct SQL injection attacks. It is also possible to bypass access restriction mechanisms (e.g., try anonymous connections). If user credentials are not necessary for exploiting this vulnerability, then this can be exploited by administrators. Exploitation of this vulnerability results in unauthorized access to Oracle JDeveloper. Mitigation For Oracle JDeveloper users, it is recommended to update to the latest version. For administrators, it is recommended to review Oracle JDeveloper configuration and access control settings. Vulnerable versions The following versions are vulnerable to this issue: 220.127.116.11.0 18.104.22.168.0 22.214.171.124.0 126.96.36.199.0 188.8.131.52.0 184.108.40.206.1 220.127.116.11.0 18.104.22.168.0 22.214.171.124.1 126.96.36.199.1 188.8.131.52.2 184.108.40.206.0 220.127.116.11.0 18.104.22.168.1 22.214.171.124.1 126.96.36.199.2 188.8.131.52.2 184.108.40.206.3 220.127.116.11.3 18.104.22.168.4 22.214.171.124.4
How to determine which version of Oracle JDeveloper is installed?
To determine which version of Oracle JDeveloper is installed, log in to the JDeveloper console and go to Tools > Java Control Panel.
So, what does this vulnerability entail? Users must have "viewdata" permission for a database that uses the Oracle JDeveloper SQL interface. The only way to exploit this vulnerability is if your user account has write access permissions for the database.