Oracle Java up to 7 Update 17 RMI memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in Oracle Java up to 7 Update 17. This affects an unknown function of the component RMI. This manipulation causes memory corruption. The identification of this vulnerability is CVE-2013-1557. There is no exploit available. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability was found in Oracle Java up to 7 Update 17 (Programming Language Software). It has been declared as very critical. Affected by this vulnerability is some unknown functionality of the component RMI. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

Unspecified vulnerability in the Java Runtime Environment (JRE) component in Oracle Java SE 7 Update 17 and earlier, 6 Update 43 and earlier, and 5.0 Update 41 and earlier; and OpenJDK 6 and 7; allows remote attackers to affect confidentiality, integrity, and availability via vectors related to RMI. NOTE: the previous information is from the April 2013 CPU. Oracle has not commented on claims from another vendor that this issue is related to "missing security restrictions" in the LogStream.setDefaultStream method.

The weakness was shared 04/16/2013 with Oracle as Oracle Java SE Critical Patch Update Advisory - April 2013 as not defined advisory (Website). The advisory is shared at oracle.com. This vulnerability is known as CVE-2013-1557 since 01/30/2013. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 05/08/2021). It is expected to see the exploit prices for this product decreasing in the near future.

The vulnerability scanner Nessus provides a plugin with the ID 69742 (Amazon Linux AMI : java-1.7.0-openjdk (ALAS-2013-183)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Amazon Linux Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 185051 (HP-UX Running Java5 Multiple Vulnerabilities (HPSBUX02922)).

Applying a patch is able to eliminate this problem. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (83572), Tenable (69742), SecurityFocus (BID 59170†) and Vulnerability Center (SBV-49041†). Additional details are provided at zdnet.com. The entries VDB-7986, VDB-7987, VDB-7988 and VDB-8038 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 69742
Nessus Name: Amazon Linux AMI : java-1.7.0-openjdk (ALAS-2013-183)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

OpenVAS ID: 881715
OpenVAS Name: CentOS Update for java CESA-2013:0751 centos6
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Patch
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

01/30/2013 🔍
04/16/2013 +76 days 🔍
04/16/2013 +0 days 🔍
04/16/2013 +0 days 🔍
04/17/2013 +1 days 🔍
04/17/2013 +0 days 🔍
11/05/2014 +567 days 🔍
03/12/2015 +127 days 🔍
05/08/2021 +2249 days 🔍

Sourcesinfo

Vendor: oracle.com

Advisory: Oracle Java SE Critical Patch Update Advisory - April 2013
Organization: Oracle
Status: Not defined
Confirmation: 🔍

CVE: CVE-2013-1557 (🔍)
GCVE (CVE): GCVE-0-2013-1557
GCVE (VulDB): GCVE-100-8269

OVAL: 🔍
IAVM: 🔍

X-Force: 83572
SecurityFocus: 59170 - Oracle Java SE CVE-2013-1557 Remote Java Runtime Environment Vulnerability
Vulnerability Center: 49041 - [javacpuapr2013-1928497] Oracle JRE RMI Remote Code Execution Vulnerability (CVE-2013-1557), Critical

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 04/17/2013 11:51
Updated: 05/08/2021 09:44
Changes: 04/17/2013 11:51 (80), 06/22/2017 10:48 (3), 05/08/2021 09:44 (2)
Complete: 🔍
Cache ID: 216:3D0:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!