Paul Fiterau Brostean

The issue is related to insufficient access control in the JSSE component of Java SE, allowing an unauthenticated attacker with network access via HTTPS to compromise Java SE. Successful attacks can result in unauthorized update, insert, or delete access to some of Java SE's accessible data, as well as unauthorized read access to a subset of Java SE's accessible data. This issue can be exploited through sandboxed Java Web Start applications, sandboxed Java applets, or by supplying data to APIs in the specified component without using sandboxed applications or applets.

The issue is related to a vulnerability in the Java Secure Socket Extension (JSSE) component of Oracle Java SE, which is difficult to exploit and allows an unauthenticated attacker with network access via HTTPS to compromise Java SE. This can result in unauthorized update, insert, or delete access to some of Java SE's accessible data, as well as unauthorized read access to a subset of Java SE's accessible data. The vulnerability applies to Java deployments that load and run untrusted code and rely on the Java sandbox for security. It can also be exploited by using APIs in the specified component.

The issue is related to inadequate access control in the Consolidation Infrastructure component of Oracle Solaris, allowing a low-privileged attacker with logon access to the infrastructure to compromise Oracle Solaris. Successful attacks require human interaction from a person other than the attacker and can significantly impact additional products, potentially resulting in the takeover of Oracle Solaris.

The issue allows code injection if the first argument to `Shell#[]` or `Shell#test` in lib/shell.rb is untrusted data. An attacker can exploit this to call an arbitrary Ruby method. This is due to incorrect neutralization of special elements in output used by an incoming component.