CVE-2016-5573: High severity oracle java se 7 vulnerability

Published Oct 17, 2016
·
Updated

It was discovered that the Hotspot component of OpenJDK did not properly check Java Debug Wire Protocol (JDWP) packets, which could possibly allow HTTP requests issues by a web browser to be interpreted as valid JDWP messages. An attacker could possibly use this flaw to send debugging commands to a Java program or applet running with debugging enabled if they could make victim's browser send HTTP requests to the JDWP port of the debugged application.

Other sources

Unspecified vulnerability in Oracle Java SE 6u121, 7u111, 8u102; and Java SE Embedded 8u101 allows remote attackers to affect confidentiality, integrity, and availability via vectors related to Hotspot, a different vulnerability than CVE-2016-5582.

MITRE

Affected Software

8 affected components
Oracle JDK=1.6.0-update121
Oracle JDK=1.7.0-update111
Oracle JDK=1.8.0-update101
Oracle JDK=1.8.0-update102
ORACLE JRE=1.6.0-update121
ORACLE JRE=1.7.0-update111
ORACLE JRE=1.8.0-update101
ORACLE JRE=1.8.0-update102

Event History

Oct 17, 2016
Data Sourced
via Red Hat·09:59 AM
DescriptionSeverityAffected Software
Oct 25, 2016
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2016-5573?

CVE-2016-5573 has a severity rating that indicates it poses a risk of remote code execution under certain circumstances.

2

How do I fix CVE-2016-5573?

To fix CVE-2016-5573, update to an affected version of OpenJDK or apply the appropriate security patches provided by Oracle.

3

Which software versions are affected by CVE-2016-5573?

CVE-2016-5573 affects Oracle JDK and JRE versions 1.6.0-update121, 1.7.0-update111, and 1.8.0-update101 and 1.8.0-update102.

4

What are the potential exploits of CVE-2016-5573?

An attacker could exploit CVE-2016-5573 to send malicious commands via the Java Debug Wire Protocol, allowing them to control the affected system.

5

Is there a public exploit available for CVE-2016-5573?

As of the latest information, there are no known public exploits specifically targeting CVE-2016-5573.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203