CVE-2016-5528: Oracle GlassFish Server compromise in Security subcomponent

CVE-2016-5528 · Severity: critical · CVSS 9 · Published 2017-01-27

Oracle GlassFish Server, a platform used for developing and deploying Java applications, contains a critical security vulnerability. An unauthorized attacker could remotely exploit this flaw to take full control of the server. Such an attack could lead to the theft of sensitive data, disruption of business operations, and potential unauthorized access to other connected systems.

Technologies: Oracle Glassfish Server. Vendors: Oracle.

Quick answers

Is CVE-2016-5528 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2016-5528 being exploited in the wild.
How severe is CVE-2016-5528?
Critical severity, with a CVSS score of 9, published 27 January 2017.
Which products and versions are affected?
Oracle Glassfish Server 2.1.1, 3.0.1, 3.1.2.
Is there a fix for CVE-2016-5528?
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-5528 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2016-5528?
Check whether you run Oracle Glassfish Server 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 exists in the Security subcomponent of Oracle GlassFish Server versions 2.1.1, 3.0.1, and 3.1.2. It is classified as a high-complexity attack that can be executed by an unauthenticated attacker with network access via multiple protocols. Successful exploitation results in a complete takeover of the GlassFish Server (impacting Confidentiality, Integrity, and Availability) and carries a 'Scope' change, meaning the impact can extend beyond the GlassFish environment to other products. Oracle addressed this issue in the January 2017 Critical Patch Update.

Affected products

  • Oracle GlassFish Server 2.1.1, 3.0.1, 3.1.2

Timeline

  • 2017-01-27: disclosed
  • 2017-01-27: advisory: Oracle Critical Patch Update published

References

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