Why is Java disabled in Chrome? It is some security concern?
The reasons prompting the disabling of NPAPI, and therefore Java, include the following according to the Chromium Blog:
- Increased security
- Increased speed
- Increased stability
- Reduction in code complexity
- Reduction in crashes
- Reduction in hangs
- Lack of support for mobile devices
How it could be dangerous for Chrome users with latest version of Java JRE installed?
Short answer: Zero Day Exploits.
Another source for vulnerabilities is the fact that Java hasn’t released an automatic updater that doesn’t require user intervention and administrative rights. For example, Google Chrome and Flash Player have. This feature allows users to get automatic updates without being prompted to take action, making updates easier.
For lack of an automatic updates system, many users ignore Java
updates and even fear installing them, because of malware that used
Java updates as an infection vector in the past or similar
Just know that all these vulnerabilities are what cyber criminals
Data extracted from our own database confirms that Java is the second
biggest security vulnerability that requires constant patching, after
Adobe’s Flash plugin.
In 2015 alone, we’ve already deployed 105925 patches for Java Runtime
Environment for our clients.
Read the rest of the article for a detailed explanation and commentary.
Source Why are Java’s Vulnerabilities One of the Biggest Security Holes on Your Computer?
The Final Countdown for NPAPI
Last September we announced our plan to remove NPAPI support from Chrome, a change that will improve Chrome’s security, speed, and stability as well as reduce complexity in the code base.
Source The Final Countdown for NPAPI
Saying Goodbye to Our Old Friend NPAPI
NPAPI’s 90s-era architecture has become a leading cause of hangs,
crashes, security incidents, and code complexity. Because of this,
Chrome will be phasing out NPAPI support over the coming year. We feel
the web is ready for this transition. NPAPI isn’t supported on mobile
devices, and Mozilla plans to make all plug-ins except the current
version of Flash click-to-play by default.
Source Saying Goodbye to Our Old Friend NPAPI