Oracle releases patch to fixed highly critical bug
Oracle fixes a critical security flaw which leads to remote code execution without the need of its users credentials. The security flaw was around for more than two years, which is first reported by the Polish security firm Security Explorations back in 2013.
The firm earlier this month publicly announced that Oracle failed to patch the critical security flaw, which they reported two years ago. Oracle announced today in a security alert today that a patch has been released which will address the security flaw, which is affecting Java SE running in web browsers on desktops.
The security flaw is considered so severe as the flaw "can impact the availability, integrity, and confidentiality of the user's system." The severity level of this security flaw is so high that Oracle recommended its users to apply the latest update as soon as possible.
In their security alert report Oracle said, "This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator)."
The firm earlier this month publicly announced that Oracle failed to patch the critical security flaw, which they reported two years ago. Oracle announced today in a security alert today that a patch has been released which will address the security flaw, which is affecting Java SE running in web browsers on desktops.
The security flaw is considered so severe as the flaw "can impact the availability, integrity, and confidentiality of the user's system." The severity level of this security flaw is so high that Oracle recommended its users to apply the latest update as soon as possible.
In their security alert report Oracle said, "This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator)."
