RedHat has issued an advisory today (October 19): https://rhn.redhat.com/errata/RHSA-2016-2079.html Corresponding Oracle CPU: http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
Whiteboard: (none) => MGA5TOO
Assigning to registered maintainer.
CC: (none) => marja11Assignee: bugsquad => mageia
See https://bugs.mageia.org/show_bug.cgi?id=14051#c4 for useful links to test java Advisory: ======================== Updated java-1.8.0-openjdk packages fix security vulnerabilities: It was discovered that the Hotspot component of OpenJDK did not properly check arguments of the System.arraycopy() function in certain cases. An untrusted Java application or applet could use this flaw to corrupt virtual machine's memory and completely bypass Java sandbox restrictions (CVE-2016-5582). It was discovered that the Hotspot component of OpenJDK did not properly check received Java Debug Wire Protocol (JDWP) packets. An attacker could possibly use this flaw to send debugging commands to a Java program running with debugging enabled if they could make victim's browser send HTTP requests to the JDWP port of the debugged application (CVE-2016-5573). It was discovered that the Libraries component of OpenJDK did not restrict the set of algorithms used for Jar integrity verification. This flaw could allow an attacker to modify content of the Jar file that used weak signing key or hash algorithm (CVE-2016-5542). Note: After this update, MD2 hash algorithm and RSA keys with less than 1024 bits are no longer allowed to be used for Jar integrity verification by default. MD5 hash algorithm is expected to be disabled by default in the future updates. A newly introduced security property jdk.jar.disabledAlgorithms can be used to control the set of disabled algorithms. A flaw was found in the way the JMX component of OpenJDK handled classloaders. An untrusted Java application or applet could use this flaw to bypass certain Java sandbox restrictions (CVE-2016-5554). A flaw was found in the way the Networking component of OpenJDK handled HTTP proxy authentication. A Java application could possibly expose HTTPS server authentication credentials via a plain text network connection to an HTTP proxy if proxy asked for authentication (CVE-2016-5597). Note: After this update, Basic HTTP proxy authentication can no longer be used when tunneling HTTPS connection through an HTTP proxy. Newly introduced system properties jdk.http.auth.proxying.disabledSchemes and jdk.http.auth.tunneling.disabledSchemes can be used to control which authentication schemes can be requested by an HTTP proxy when proxying HTTP and HTTPS connections respectively. References: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5542 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5554 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5573 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5582 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-5597 http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html https://rhn.redhat.com/errata/RHSA-2016-2079.html ======================== Updated packages in core/updates_testing: ======================== java-1.8.0-openjdk-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-headless-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-devel-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-demo-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-src-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-javadoc-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-accessibility-1.8.0.111-1.b16.1.mga5 from java-1.8.0-openjdk-1.8.0.111-1.b16.1.mga5.src.rpm
Version: Cauldron => 5Assignee: mageia => qa-bugsWhiteboard: MGA5TOO => has_procedure
Prior to testing, the test links referred to in Comment 2: http://www.w3.org/People/mimasa/test/object/java/ http://www.java.com/en/download/installed.jsp http://javatester.org/version.html http://www.addictinggames.com/action-games/index.jsp [for a choice] + another from https://bugs.mageia.org/show_bug.cgi?id=19002#c5 <quote> I ran into some problems with the test procedure: 1. The applets in the first link are too 'whack-a-mole'-y and don't work. 2. The fourth link [with ../stickman-downhill-game.jsp] does not work. I used instead: </quote> https://docs.oracle.com/javase/tutorial/deployment/applet/examplesIndex.html
CC: (none) => lewyssmith
Testing M5-64 real h/w; after the update: java-1.8.0-openjdk-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-headless-1.8.0.111-1.b16.1.mga5 Using Firefox Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Firefox/45.0 I found at the second & third test URLs (above) that this did not seem to have Java; nor could I find anything chez Mageia which resembled a Firefox Java addon, plugin, extension. A search revealed: "The 64-bit version of Firefox, released in December 2015, does not support the Java plugin. .. If you see "Win64" or "x64," you're using the 64-bit version and can't use Java." Trying also Opera 12 - which also lacked the plugin... Trying all the test links, almost nothing worked except (Opera only) some of the games. It seems a waste of time trying this thing without the browser Java plugin. I did run into pages offering to download it; worth following? Any advice welcome. Is there any way of testing Java *locally* without a browser?
Do you have icedtea-web installed? "The IcedTea-Web project provides a Java web browser plugin..."
CC: (none) => jim
Before updating: $ rpm -qa | grep openjdk java-1.8.0-openjdk-1.8.0.102-1.b14.1.mga5 java-1.8.0-openjdk-headless-1.8.0.102-1.b14.1.mga5 http://javatester.org/version.html The java applet executed and displayed my java version as 1.8.0_102 After updating: $ rpm -qa | grep openjdk java-1.8.0-openjdk-headless-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-1.8.0.111-1.b16.1.mga5 http://javatester.org/version.html The applet executed and displayed my java version as 1.8.0_111 The applet executed and displayed: "You have the recommended Java installed (Version 8 Update 111)." OK for mga5-64
Whiteboard: has_procedure => has_procedure MGA5-64-OK
The result of the second test should read: https://www.java.com/en/download/installed.jsp The applet executed and displayed: "You have the recommended Java installed (Version 8 Update 111)." I omitted the URL from comment6
(In reply to James Kerr from comment #5) > Do you have icedtea-web installed? No. I installed it, and re-ran tests as described below (even if only to learn; duplicating your x64 testing). What did *you* have in the way of browser & Java plug-in? java-1.8.0-openjdk-1.8.0.111-1.b16.1.mga5 java-1.8.0-openjdk-headless-1.8.0.111-1.b16.1.mga5 Re-testing with Firefox 45, IcedTea-web installed, checked that Firefox knew it had the plugin. M5-64, real hardware. Note that every test involved a lot of clicking 'yes', 'continue', 'run', 'allow' dialogues, again & again; and sometimes the Java element itself on the page to start it off. http://www.w3.org/People/mimasa/test/object/java/ This has 5 tests. The first eventually showed correctly two rows of clocks. The rest ended just with large grey boxes. http://www.java.com/en/download/installed.jsp Eventually showed: "Congratulations! You have the recommended Java installed (Version 8 Update 111)." http://javatester.org/version.html Eventually showed its pink rectangle with the correct Java version 1.8.0_111. https://docs.oracle.com/javase/tutorial/deployment/applet/examplesIndex.html This has many tests, not all of which worked. e.g. "Applet With Customized Loading Progress Indicator" after a long time showed a scrollable table of cities and their temperatures. "Dynamic Tree Demo Applet" produced a clever interactive tree application. "Sender Receiver Applets" showed an simple application which worked. Seconding James' x64 OK.
Keywords: (none) => validated_updateWhiteboard: has_procedure MGA5-64-OK => has_procedure MGA5-64-OK advisoryCC: (none) => davidwhodgins, sysadmin-bugs
(In reply to Lewis Smith from comment #8) > What did *you* have in the way of browser & Java plug-in? > I have: $ rpm -q firefox icedtea-web firefox-45.4.0-2.mga5 icedtea-web-1.6.2-1.mga5 icedtea-web was installed by default, but that could be because I did a network install (selecting the KDE option). This is a fresh install of mga5 (less than a week ago). When testing the applets, I also had to click through numerous warnings about how dangerous it is to run java applets, just as you did.
An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2016-0359.html
Status: NEW => RESOLVEDResolution: (none) => FIXED