Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

为提升您的使用体验，本站正在维护，部分功能暂时无法使用。如果本站文章无法解决您的问题，您想要向社区提问的话，请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问，我们的支持社区将会很快回复您的疑问。

Avatar for Username

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信，及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

话题已存档。 如果需要帮助请提出新问题。

Bug in Plugin Check's status report is a security problem

  • 2 个回答
  • 1 人有此问题
  • 7 次查看
  • 最后回复者为 n0diamond

n0diamond
n0diamond
more options

Plugin Status (https://www.mozilla.org/en-US/plugincheck/) says "Java(TM) Platform SE 7 U65" "Up to Date 10.65.2.20". This is wrong. I have already started installing U67 because U65 is obsolete. The false report likely persuades users not to update.

Plugin Status also says "Java Deployment Toolkit 7.0.650.20" "Up to Date 10.65.2.20". I don't know yet if that is true or not. If the Platform update doesn't also update the Deployment Toolkit then I'll try to find that update. This is a big security problem because a different page reports that Java Deployment Toolkit 7.0.650.20 has a known vulnerability.

Plugin Status (https://www.mozilla.org/en-US/plugincheck/) says "Java(TM) Platform SE 7 U65" "Up to Date 10.65.2.20". This is wrong. I have already started installing U67 because U65 is obsolete. The false report likely persuades users not to update. Plugin Status also says "Java Deployment Toolkit 7.0.650.20" "Up to Date 10.65.2.20". I don't know yet if that is true or not. If the Platform update doesn't also update the Deployment Toolkit then I'll try to find that update. This is a big security problem because a different page reports that Java Deployment Toolkit 7.0.650.20 has a known vulnerability.

所有回复 (2)

guigs
guigs
more options

There is a bug on file for that, I would track the changes there: https://bugzilla.mozilla.org/show_bug.cgi?id=1052877

n0diamond
n0diamond 提问者
more options

There are several bugs in that bug report and it's still buggy. Thank you for pointing me to it though.