CVE-2009-3547 : 상세 정보

CVE-2009-3547

7
/
높음
2.01%V4
2009-11-04
15h00 +00:00
Memory Corruption
Local
2024-08-07
06h31 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

Multiple race conditions in fs/pipe.c in the Linux kernel before 2.6.32-rc6 allow local users to cause a denial of service (NULL pointer dereference and system crash) or gain privileges by attempting to open an anonymous pipe via a /proc/*/fd/ pathname.

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-476 NULL Pointer Dereference
The product dereferences a pointer that it expects to be valid but is NULL.
CWE-672 Operation on a Resource after Expiration or Release
The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.1 7 HIGH CVSS:3.1/AV:L/AC:H/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.

High

successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected.

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 6.9 AV:L/AC:M/Au:N/C:C/I:C/A:C nvd@nist.gov

EPSS

EPSS는 취약점이 악용될 가능성을 예측하는 점수 모델입니다.

EPSS 점수

EPSS 모델은 0과 1(0~100%) 사이의 확률 점수를 생성합니다. 점수가 높을수록 취약점이 악용될 가능성이 높습니다.

EPSS 백분위수

백분위수는 EPSS 점수에 따라 CVE의 순위를 매기는 데 사용됩니다. 예를 들어 EPSS 점수 기준 95번째 백분위수의 CVE는 다른 CVE의 95%보다 악용될 가능성이 높습니다.

익스플로잇 정보

Exploit Database EDB-ID : 9844

게시일 : 2009-11-04 23h00 +00:00
저자 : Matthew Bergin
EDB 검증됨 : Yes

Exploit Database EDB-ID : 33321

게시일 : 2009-11-02 23h00 +00:00
저자 : teach & xipe
EDB 검증됨 : Yes

Exploit Database EDB-ID : 40812

게시일 : 2013-12-15 23h00 +00:00
저자 : spender
EDB 검증됨 : No

Exploit Database EDB-ID : 10018

게시일 : 2009-11-11 23h00 +00:00
저자 : Earl Chew
EDB 검증됨 : Yes

Exploit Database EDB-ID : 33322

게시일 : 2009-11-02 23h00 +00:00
저자 : teach & xipe
EDB 검증됨 : Yes

언급된 제품

구성 0

Linux>>Linux_kernel >> Version 까지 (포함) 2.6.31.14

Linux>>Linux_kernel >> Version 2.6.32

Linux>>Linux_kernel >> Version 2.6.32

Linux>>Linux_kernel >> Version 2.6.32

Linux>>Linux_kernel >> Version 2.6.32

Linux>>Linux_kernel >> Version 2.6.32

Linux>>Linux_kernel >> Version 2.6.32

구성 0

Novell>>Linux_desktop >> Version 9

Opensuse>>Opensuse >> Version 11.0

Opensuse>>Opensuse >> Version 11.2

Suse>>Suse_linux_enterprise_desktop >> Version 10

Suse>>Suse_linux_enterprise_server >> Version 10

구성 0

Canonical>>Ubuntu_linux >> Version 6.06

Canonical>>Ubuntu_linux >> Version 8.04

Canonical>>Ubuntu_linux >> Version 8.10

Canonical>>Ubuntu_linux >> Version 9.04

Canonical>>Ubuntu_linux >> Version 9.10

구성 0

Fedoraproject>>Fedora >> Version 10

구성 0

Vmware>>Vma >> Version 4.0

Vmware>>Esx >> Version 4.0

구성 0

Redhat>>Mrg_realtime >> Version 1.0

Redhat>>Enterprise_linux_desktop >> Version 3.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.4

Redhat>>Enterprise_linux_server >> Version 3.0

Redhat>>Enterprise_linux_server >> Version 4.0

Redhat>>Enterprise_linux_server >> Version 5.0

Redhat>>Enterprise_linux_workstation >> Version 3.0

Redhat>>Enterprise_linux_workstation >> Version 4.0

Redhat>>Enterprise_linux_workstation >> Version 5.0

참고 자료

http://www.redhat.com/support/errata/RHSA-2009-1672.html
Tags : vendor-advisory, x_refsource_REDHAT
http://www.securityfocus.com/bid/36901
Tags : vdb-entry, x_refsource_BID
https://rhn.redhat.com/errata/RHSA-2009-1540.html
Tags : vendor-advisory, x_refsource_REDHAT
http://www.ubuntu.com/usn/usn-864-1
Tags : vendor-advisory, x_refsource_UBUNTU
http://secunia.com/advisories/38794
Tags : third-party-advisory, x_refsource_SECUNIA
http://lkml.org/lkml/2009/10/21/42
Tags : mailing-list, x_refsource_MLIST
https://rhn.redhat.com/errata/RHSA-2009-1541.html
Tags : vendor-advisory, x_refsource_REDHAT
http://www.mandriva.com/security/advisories?name=MDVSA-2009:329
Tags : vendor-advisory, x_refsource_MANDRIVA
http://secunia.com/advisories/37351
Tags : third-party-advisory, x_refsource_SECUNIA
http://marc.info/?l=oss-security&m=125724568017045&w=2
Tags : mailing-list, x_refsource_MLIST
https://rhn.redhat.com/errata/RHSA-2009-1548.html
Tags : vendor-advisory, x_refsource_REDHAT
http://secunia.com/advisories/38834
Tags : third-party-advisory, x_refsource_SECUNIA
http://lkml.org/lkml/2009/10/14/184
Tags : mailing-list, x_refsource_MLIST
https://rhn.redhat.com/errata/RHSA-2009-1550.html
Tags : vendor-advisory, x_refsource_REDHAT
http://secunia.com/advisories/38017
Tags : third-party-advisory, x_refsource_SECUNIA
http://www.vupen.com/english/advisories/2010/0528
Tags : vdb-entry, x_refsource_VUPEN