CVE-2009-2692 : Chi tiết

CVE-2009-2692

7.8
/
Cao
17.56%V4
2009-08-14
15h00 +00:00
Local
2024-08-07
05h59 +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

The Linux kernel 2.6.0 through 2.6.30.4, and 2.4.4 through 2.4.37.4, does not initialize all function pointers for socket operations in proto_ops structures, which allows local users to trigger a NULL pointer dereference and gain privileges by using mmap to map page zero, placing arbitrary code on this page, and then invoking an unavailable operation, as demonstrated by the sendpage operation (sock_sendpage function) on a PF_PPPOX socket.

Thông tin CVE

Điểm yếu liên quan

CWE-ID Tên điểm yếu Nguồn
CWE-908 Use of Uninitialized Resource
The product uses or accesses a resource that has not been initialized.

Số liệu

Số liệu Điểm Mức độ nghiêm trọng CVSS Vector Nguồn
V3.1 7.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/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.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

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.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

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.

nvd@nist.gov
V2 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C nvd@nist.gov

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 : 9477

Ngày xuất bản : 2009-08-17 22h00 +00:00
Tác giả : Zinx
EDB đã xác minh : Yes

Exploit Database EDB-ID : 19933

Ngày xuất bản : 2012-07-18 22h00 +00:00
Tác giả : Metasploit
EDB đã xác minh : Yes

Exploit Database EDB-ID : 9545

Ngày xuất bản : 2009-08-30 22h00 +00:00
Tác giả : Ramon de C Valle
EDB đã xác minh : Yes

Exploit Database EDB-ID : 9598

Ngày xuất bản : 2009-09-08 22h00 +00:00
Tác giả : Ramon de C Valle
EDB đã xác minh : Yes

Exploit Database EDB-ID : 9479

Ngày xuất bản : 2009-08-23 22h00 +00:00
Tác giả : INetCop Security
EDB đã xác minh : Yes

Exploit Database EDB-ID : 9641

Ngày xuất bản : 2009-09-10 22h00 +00:00
Tác giả : Ramon de C Valle
EDB đã xác minh : Yes

Exploit Database EDB-ID : 9435

Ngày xuất bản : 2009-08-13 22h00 +00:00
Tác giả : spender
EDB đã xác minh : Yes

Exploit Database EDB-ID : 9436

Ngày xuất bản : 2009-08-13 22h00 +00:00
Tác giả : Przemyslaw Frasunek
EDB đã xác minh : Yes

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

Cấu hình 0

Linux>>Linux_kernel >> Version Từ (bao gồm) 2.4.4 Đến (không bao gồm) 2.4.37.5

Linux>>Linux_kernel >> Version Từ (bao gồm) 2.6.0 Đến (không bao gồm) 2.6.30.5

Cấu hình 0

Debian>>Debian_linux >> Version 4.0

Cấu hình 0

Suse>>Linux_enterprise_real_time >> Version 10

Cấu hình 0

Redhat>>Enterprise_linux_desktop >> Version 4.0

Redhat>>Enterprise_linux_desktop >> Version 5.0

Redhat>>Enterprise_linux_eus >> Version 4.8

Redhat>>Enterprise_linux_eus >> Version 5.3

Redhat>>Enterprise_linux_server >> Version 4.0

Redhat>>Enterprise_linux_server >> Version 5.0

Redhat>>Enterprise_linux_server_aus >> Version 5.3

Redhat>>Enterprise_linux_workstation >> Version 4.0

Redhat>>Enterprise_linux_workstation >> Version 5.0

Tài liệu tham khảo

http://www.redhat.com/support/errata/RHSA-2009-1233.html
Tags : vendor-advisory, x_refsource_REDHAT
http://secunia.com/advisories/36278
Tags : third-party-advisory, x_refsource_SECUNIA
http://www.debian.org/security/2009/dsa-1865
Tags : vendor-advisory, x_refsource_DEBIAN
http://rhn.redhat.com/errata/RHSA-2009-1223.html
Tags : vendor-advisory, x_refsource_REDHAT
http://secunia.com/advisories/37298
Tags : third-party-advisory, x_refsource_SECUNIA
http://secunia.com/advisories/36430
Tags : third-party-advisory, x_refsource_SECUNIA
http://secunia.com/advisories/37471
Tags : third-party-advisory, x_refsource_SECUNIA
http://rhn.redhat.com/errata/RHSA-2009-1222.html
Tags : vendor-advisory, x_refsource_REDHAT
http://www.exploit-db.com/exploits/19933
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.vupen.com/english/advisories/2009/2272
Tags : vdb-entry, x_refsource_VUPEN
http://secunia.com/advisories/36289
Tags : third-party-advisory, x_refsource_SECUNIA
http://secunia.com/advisories/36327
Tags : third-party-advisory, x_refsource_SECUNIA
http://www.mandriva.com/security/advisories?name=MDVSA-2009:233
Tags : vendor-advisory, x_refsource_MANDRIVA
http://www.exploit-db.com/exploits/9477
Tags : exploit, x_refsource_EXPLOIT-DB
http://www.openwall.com/lists/oss-security/2009/08/14/1
Tags : mailing-list, x_refsource_MLIST
http://www.securityfocus.com/bid/36038
Tags : vdb-entry, x_refsource_BID
http://www.vupen.com/english/advisories/2009/3316
Tags : vdb-entry, x_refsource_VUPEN