Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-pagenavi domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/u918112125/domains/exploit.company/public_html/wp-includes/functions.php on line 6114
Java Version Downgrade - exploit.company
header-logo
Suggest Exploit
vendor:
Java Runtime Environment (JRE)
by:
5.5
CVSS
MEDIUM
Version Downgrade
16
CWE
Product Name: Java Runtime Environment (JRE)
Affected Version From:
Affected Version To:
Patch Exists: NO
Related CWE:
CPE: cpe:2.3:a:oracle:jre:*:*:*:*:*:*:*:*
Metasploit:
Other Scripts:
Platforms Tested: Windows, Internet Explorer

Java Version Downgrade

Java provides support for dynamic and static versioning when loading applets in the Java plug-in. This means that during the invocation of an applet, a user can request that a particular version of a plug-in be used to run the applet. The feature is accessible through various HTML tags that allow Java applets to be embedded in HTML documents, such as the EMBED, OBJECT, and APPLET tags. This feature presents a security weakness in that it may be abused to cause a previous version of a plug-in that is known to be prone to security vulnerabilities to be loaded in lieu of a more recent, fixed version. For this design flaw to pose a security threat, a vulnerable plug-in must either already be installed on the host computer or the user must manually install a version that is prone to security vulnerabilities. If a targeted version is not installed, the user may be prompted to install it. This weakness could result in a false sense of security, since the user may believe that installing an updated version will eliminate vulnerabilities in previous versions. Note that since this feature is supported in various browsers, the browsers themselves may be prone to the issue. Some browsers may not allow a Java plug-in that is no longer registered with the browser to run.

Mitigation:

Ensure that the latest version of the Java plug-in is installed and configured properly. Regularly check for updates and apply patches as soon as they are available. Be cautious when installing older versions of the plug-in, as they may be prone to security vulnerabilities.
Source

Exploit-DB raw data:

source: https://www.securityfocus.com/bid/11757/info

Java provides support for dynamic and static versioning when loading applets in the Java plug-in. This means that during the invocation of an applet, a user can request that a particular version of a plug-in be used to run the applet. The feature is accessible through various HTML tags that allow Java applets to be embedded in HTML documents, such as the EMBED, OBJECT, and APPLET tags. 

This feature presents a security weakness in that it may be abused to cause a previous version of a plug-in that is known to be prone to security vulnerabilities to be loaded in lieu of a more recent, fixed version. For this design flaw to pose a security threat, a vulnerable plug-in must either already be installed on the host computer or the user must manually install a version that is prone to security vulnerabilities. If a targeted version is not installed, the user may be prompted to install it.

This weakness could result in a false sense of security, since the user may believe that installing an updated version will eliminate vulnerabilities in previous versions. 

Note that since this feature is supported in various browsers, the browsers themselves may be prone to the issue. Some browsers may not allow a Java plug-in that is no longer registered with the browser to run. 

<html> 
<title> Java Version Downgrade proof-of-concept </title> 
<body> 
Demonstration uses the following vulnerability: 
<br> 
https://www.securityfocus.com/bid/8879 
<br> 
Source code for Simple.class: 
<br> 
https://www.securityfocus.com/bid/8879/exploit/ 
<p> 
Added this code to Simple.java for debugging purposes: 
<br> 
String javaVersion = System.getProperty("java.version"); 
<br> 
addItem("Java version: " + javaVersion); 
<p> 
This proof-of-concept was tested on a Windows system using IE with 
the following Java installations: 
<br> 
Sun JRE 1.3.1_07 (vulnerable to BID 8879) 
<br> 
Sun JRE 1.3.1_13 (not vulnerable to BID 8879) 
<br> 
note: invoking applet normally should run Simple.class in JRE 
1.3.1_13. 
<p> 
<OBJECT classid="clsid:CAFEEFAC-0013-0001-0007-ABCDEFFEDCBA" 
width = "600" height = "100" 
codebase="http://java.sun.com/products/plugin/autodl/jinstall-1_3_1_07-windows-i586.cab##Version=1_3_1_07"> 
<PARAM NAME="code" VALUE="Simple.class"> 
</OBJECT> 
</body> 
</html>