GPT-Load through 1.4.11 Cleartext Proxy Key Logging via Access Logger
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| tbphp | gpt-load | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Tbphp | Gpt-load |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.110% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tbphp
Tbphp gpt-load |
|
| Vendors & Products |
Tbphp
Tbphp gpt-load |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | GPT-Load through 1.4.11 contains a cleartext logging vulnerability that exposes client proxy keys because the Gin Logger middleware records the raw query string before extractAuthKey strips the key parameter. Attackers with read access to console logs or ./data/logs/app.log can recover proxy keys from Gemini-style requests and use them against the corresponding group. | |
| Title | GPT-Load through 1.4.11 Cleartext Proxy Key Logging via Access Logger | |
| Weaknesses | CWE-532 | |
| References |
|
|
| Metrics |
cvssV3_1
|