| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in HAProxy and classified as problematic. The impacted element is an unknown function of the component HTTP Header Handler. This manipulation of the argument Set-Cookie2 causes resource consumption. This vulnerability appears as CVE-2022-0711. The attack may be initiated remotely. There is no available exploit. It is suggested to install a patch to address this issue.
Details
A vulnerability classified as problematic was found in HAProxy (Firewall Software) (the affected version unknown). Affected by this vulnerability is an unknown part of the component HTTP Header Handler. The manipulation of the argument Set-Cookie2 with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability.
The weakness was presented 03/03/2022 as bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8. The advisory is shared at github.com. This vulnerability is known as CVE-2022-0711 since 02/21/2022. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Applying the patch bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8 is able to eliminate this problem. The bugfix is ready for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
License
Website
- Product: https://github.com/haproxy/haproxy/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8
Timeline
02/21/2022 🔍03/03/2022 🔍
03/03/2022 🔍
03/04/2022 🔍
Sources
Product: github.comAdvisory: bfb15ab34ead85f64cd6da0e9fb418c9cd14cee8
Status: Confirmed
CVE: CVE-2022-0711 (🔍)
GCVE (CVE): GCVE-0-2022-0711
GCVE (VulDB): GCVE-100-194113
Entry
Created: 03/03/2022 08:21Updated: 03/04/2022 18:35
Changes: 03/03/2022 08:21 (41), 03/04/2022 18:35 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.