Is CVE-2016-8328 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-8328 being exploited in the wild.

How severe is CVE-2016-8328?

Low severity, with a CVSS score of 3.7, published 27 January 2017.

Is there a fix for CVE-2016-8328?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2016-8328 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2016-8328?

Check whether you run Oracle Java SE, Oracle Jdk or Oracle JRE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-8328: Oracle Java SE integrity vulnerability in Java Mission Control

CVE-2016-8328 · Severity: low · CVSS 3.7 · Published 2017-01-27

A vulnerability exists in Oracle Java Mission Control, a tool used for monitoring and managing Java applications. An attacker could potentially modify or delete certain data within the Java environment. While the impact is limited to data integrity, it could affect the reliability of application monitoring and management tasks.

Technologies: Oracle Java SE, Oracle Jdk, Oracle JRE. Vendors: Oracle.

Quick answers

Is CVE-2016-8328 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-8328 being exploited in the wild.
How severe is CVE-2016-8328?: Low severity, with a CVSS score of 3.7, published 27 January 2017.
Which products and versions are affected?: Oracle Java SE 8u112.
Is there a fix for CVE-2016-8328?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2016-8328 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-8328?: Check whether you run Oracle Java SE, Oracle Jdk or Oracle JRE at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

This vulnerability affects the Java Mission Control (JMC) component of Oracle Java SE version 8u112. It is characterized as a difficult-to-exploit flaw that allows an unauthenticated attacker with network access via multiple protocols to compromise the integrity of Java SE data. Specifically, successful exploitation can result in unauthorized update, insert, or delete access to some Java SE accessible data. The vulnerability was addressed in the Oracle January 2017 Critical Patch Update, with version 8u121 and later being unaffected.

Affected products

Oracle Java SE 8u112

Timeline

2017-01-19: advisory: Red Hat security advisory issued
2017-01-27: disclosed: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.