CVE-2013-0422 : Chi tiết

CVE-2013-0422

9.8
/
Nghiêm trọng
93.61%V4
2013-01-10
21h23 +00:00
A01-Broken Access Control
Network
2025-10-22
00h05 +00:00
Thông báo cho một CVE
Luôn được thông báo về mọi thay đổi đối với một CVE cụ thể.
Quản lý thông báo

Mô tả CVE

Multiple vulnerabilities in Oracle Java 7 before Update 11 allow remote attackers to execute arbitrary code by (1) using the public getMBeanInstantiator method in the JmxMBeanServer class to obtain a reference to a private MBeanInstantiator object, then retrieving arbitrary Class references using the findClass method, and (2) using the Reflection API with recursion in a way that bypasses a security check by the java.lang.invoke.MethodHandles.Lookup.checkSecurityManager method due to the inability of the sun.reflect.Reflection.getCallerClass method to skip frames related to the new reflection API, as exploited in the wild in January 2013, as demonstrated by Blackhole and Nuclear Pack, and a different vulnerability than CVE-2012-4681 and CVE-2012-3174. NOTE: some parties have mapped the recursive Reflection API issue to CVE-2012-3174, but CVE-2012-3174 is for a different vulnerability whose details are not public as of 20130114. CVE-2013-0422 covers both the JMX/MBean and Reflection API issues. NOTE: it was originally reported that Java 6 was also vulnerable, but the reporter has retracted this claim, stating that Java 6 is not exploitable because the relevant code is called in a way that does not bypass security checks. NOTE: as of 20130114, a reliable third party has claimed that the findClass/MBeanInstantiator vector was not fixed in Oracle Java 7 Update 11. If there is still a vulnerable condition, then a separate CVE identifier might be created for the unfixed issue.

Thông tin CVE

Điểm yếu liên quan

CWE-ID Tên điểm yếu Nguồn
CWE-284 Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Số liệu

Số liệu Điểm Mức độ nghiêm trọng CVSS Vector Nguồn
V3.1 9.8 CRITICAL CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

None

The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

High

There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

134c704f-9b21-4f2e-91b3-4a467353bcc0
V2 10 AV:N/AC:L/Au:N/C:C/I:C/A:C nvd@nist.gov

CISA KEV (Lỗ hổng đã bị khai thác đã biết)

Tên lỗ hổng : Oracle JRE Remote Code Execution Vulnerability

Hành động bắt buộc : Apply updates per vendor instructions.

Được biết là sử dụng trong các chiến dịch Ransomware : Known

Đã thêm : 2022-05-25 00h00 +00:00

Hành động đến hạn : 2022-06-15 00h00 +00:00

Thông tin quan trọng
CVE này được xác định là dễ bị tấn công và đặt ra mối đe dọa tích cực, theo Danh mục lỗ hổng đã bị khai thác đã biết (CISA KEV). CISA đã liệt kê lỗ hổng này là đang bị tội phạm mạng khai thác tích cực, nhấn mạnh tầm quan trọng của việc hành động ngay lập tức để giải quyết lỗ hổng này. Cần ưu tiên cập nhật và khắc phục CVE này để bảo vệ hệ thống khỏi các cuộc tấn công mạng tiềm ẩn.

EPSS

EPSS là mô hình tính điểm dự đoán khả năng một lỗ hổng bị khai thác.

Điểm EPSS

Mô hình EPSS tạo ra điểm xác suất từ 0 đến 1 (0 đến 100%). Điểm càng cao, xác suất một lỗ hổng bị khai thác càng lớn.

Phân vị EPSS

Phân vị được dùng để xếp hạng CVE theo điểm EPSS. Ví dụ, một CVE ở phân vị thứ 95 theo điểm EPSS có nhiều khả năng bị khai thác hơn 95% CVE khác. Do đó, phân vị được dùng để so sánh điểm EPSS của một CVE với các CVE khác.

Thông tin khai thác

Exploit Database EDB-ID : 24045

Ngày xuất bản : 2013-01-10 23h00 +00:00
Tác giả : Metasploit
EDB đã xác minh : Yes

Sản phẩm được đề cập

Cấu hình 0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jdk >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Oracle>>Jre >> Version 1.7.0

Cấu hình 0

Canonical>>Ubuntu_linux >> Version 12.10

Opensuse>>Opensuse >> Version 12.2

Tài liệu tham khảo

http://rhn.redhat.com/errata/RHSA-2013-0156.html
Tags : vendor-advisory, x_refsource_REDHAT
http://www.mandriva.com/security/advisories?name=MDVSA-2013:095
Tags : vendor-advisory, x_refsource_MANDRIVA
http://rhn.redhat.com/errata/RHSA-2013-0165.html
Tags : vendor-advisory, x_refsource_REDHAT
http://www.kb.cert.org/vuls/id/625617
Tags : third-party-advisory, x_refsource_CERT-VN
http://www.us-cert.gov/cas/techalerts/TA13-010A.html
Tags : third-party-advisory, x_refsource_CERT
http://www.ubuntu.com/usn/USN-1693-1
Tags : vendor-advisory, x_refsource_UBUNTU
http://seclists.org/bugtraq/2013/Jan/48
Tags : mailing-list, x_refsource_BUGTRAQ