CVE-2022-32205 : 상세 정보

CVE-2022-32205

4.3
/
보통
2.19%V4
2022-07-07
00h00 +00:00
Network
2026-10-14
16h33 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on `foo.example.com` can set cookies that also would match for `bar.example.com`, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE-770 Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.1 4.3 MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L

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.

Required

Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited. For example, a successful exploit may only be possible during the installation of an application by a system administrator.

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.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

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

None

There is no loss of integrity within the impacted component.

Availability Impact

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

Low

Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

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

EPSS

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

EPSS 점수

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

EPSS 백분위수

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

언급된 제품

구성 0

Haxx>>Curl >> Version 부터 (포함) 7.71.0 까지 (미포함) 7.84.0

구성 0

Fedoraproject>>Fedora >> Version 35

구성 0

Debian>>Debian_linux >> Version 11.0

구성 0

Netapp>>Clustered_data_ontap >> Version -

Netapp>>Element_software >> Version -

Netapp>>Hci_management_node >> Version -

Netapp>>Solidfire >> Version -

구성 0

Netapp>>H300s >> Version -

Netapp>>H300s_firmware >> Version -

구성 0

Netapp>>H500s >> Version -

Netapp>>H500s_firmware >> Version -

구성 0

Netapp>>H700s >> Version -

Netapp>>H700s_firmware >> Version -

구성 0

Netapp>>H410s >> Version -

Netapp>>H410s_firmware >> Version -

구성 0

Apple>>Macos >> Version 까지 (미포함) 13.0

구성 0

Siemens>>Scalance_sc622-2c_firmware >> Version 까지 (미포함) 3.0

Siemens>>Scalance_sc622-2c >> Version -

구성 0

Siemens>>Scalance_sc626-2c_firmware >> Version 까지 (미포함) 3.0

Siemens>>Scalance_sc626-2c >> Version -

구성 0

Siemens>>Scalance_sc632-2c_firmware >> Version 까지 (미포함) 3.0

Siemens>>Scalance_sc632-2c >> Version -

구성 0

Siemens>>Scalance_sc636-2c_firmware >> Version 까지 (미포함) 3.0

Siemens>>Scalance_sc636-2c >> Version -

구성 0

Siemens>>Scalance_sc642-2c_firmware >> Version 까지 (미포함) 3.0

Siemens>>Scalance_sc642-2c >> Version -

구성 0

Siemens>>Scalance_sc646-2c_firmware >> Version 까지 (미포함) 3.0

Siemens>>Scalance_sc646-2c >> Version -

구성 0

Splunk>>Universal_forwarder >> Version 부터 (포함) 8.2.0 까지 (미포함) 8.2.12

Splunk>>Universal_forwarder >> Version 부터 (포함) 9.0.0 까지 (미포함) 9.0.6

Splunk>>Universal_forwarder >> Version 9.1.0

참고 자료

https://hackerone.com/reports/1569946
Tags : Exploit, Third Party Advisory
https://support.apple.com/kb/HT213488
Tags : Third Party Advisory