haproxy: does not ensure that the scheme and path portions of a URI have the expected characters
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
Configuration 3 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.8 | |||
| haproxy-0:2.2.13-2.el8 | cpe:/a:redhat:openshift:4.8::el7 | RHSA-2021:5208 | 2022-01-05T00:00:00Z |
| Red Hat OpenShift Container Platform 4.9 | |||
| haproxy-0:2.2.15-2.el8 | cpe:/a:redhat:openshift:4.9::el8 | RHSA-2021:4118 | 2021-11-10T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2021-25602 | An issue was discovered in HAProxy 2.2 before 2.2.16, 2.3 before 2.3.13, and 2.4 before 2.4.3. It does not ensure that the scheme and path portions of a URI have the expected characters. For example, the authority field (as observed on a target HTTP/2 server) might differ from what the routing rules were intended to achieve. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 2.2% (2.210% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.