Higress before 2.2.4 Rate Limit Bypass via Malformed Cookie Header
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| higress-group | higress | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Higress-group | Higress |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.517% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Higress-group
Higress-group higress |
|
| Vendors & Products |
Higress-group
Higress-group higress |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Higress before 2.2.4 panics when processing a Cookie header segment without an equals sign, causing the plugin wrapper to recover and return a continue action that bypasses AI token rate limiting. Unauthenticated attackers can craft a malformed Cookie header to skip rate limit checks and exceed thresholds intended to restrict costly model backend calls. | |
| Title | Higress before 2.2.4 Rate Limit Bypass via Malformed Cookie Header | |
| Weaknesses | CWE-703 | |
| References |
|
|
| Metrics |
cvssV3_1
|