Update plugincheck for Java 7u7

RESOLVED FIXED

Status

--
critical
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: scoobidiver, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

7 years ago
Java has released Java 7u7 with a fix for CVE-2012-4681.
Tomcat, Kev,

We'd like to get this updated as soon as possible.  Can one of you jump into https://plugins.mozilla.org/en-us/login and make the change for https://plugins.mozilla.org/en-us/plugins/detail/java-runtime-environment

thanks
thats done now and also live
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
verified fixed http://screencast.com/t/35Uvs7aJOYUt
Status: RESOLVED → VERIFIED
(Quoting Anthony Hughes, Mozilla QA (:ashughes) from bug 787136 comment #10)
> Something I noticed when testing the staged block:
>  * Java 7u6 reports in PFS as "out of date" (yellow)
>  * Java 7u5 reports in PFS as "vulnerable" (red)
> 
> I think we'd want to communicate both as vulnerable.

(Quoting Michael Coates [:mcoates] from comment #11)
> (In reply to Anthony Hughes, Mozilla QA (:ashughes) from bug 787136 comment #10)
> > Something I noticed when testing the staged block:
> >  * Java 7u6 reports in PFS as "out of date" (yellow)
> >  * Java 7u5 reports in PFS as "vulnerable" (red)
> > 
> > I think we'd want to communicate both as vulnerable.
> 
> reopened to address comment 10

I believe this also applies to 1.7.0.0 - 1.7.0.3 based on looking at the entries at https://plugins.mozilla.org/en-us/plugins/detail/java-runtime-environment
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
According to bug 787136 comment 10, Java 7u6 is not being flagged as vulnerable, and it should. This is the last bit blocking the Java blocklist, so we need this fixed ASAP.
Blocks: 785837
Kev just fixed this. With consideration for caching it should be good by 3pm.
I confirm that this is now fixed. Both Java 7u6 and 7u5 appear as "vulnerable". Marking resolved fixed.
Status: REOPENED → RESOLVED
Last Resolved: 7 years ago7 years ago
Resolution: --- → FIXED
Duplicate of this bug: 788065
You need to log in before you can comment on or make changes to this bug.