axios4go's Race Condition in Shared HTTP Client Allows Proxy Configuration Leak
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| rezmoss | axios4go | affected |
|
No data.
No data available yet.
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.408% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Rezmoss
Rezmoss axios4go |
|
| CPEs | cpe:2.3:a:rezmoss:axios4go:*:*:*:*:*:go:*:* | |
| Vendors & Products |
Rezmoss
Rezmoss axios4go |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | axios4go is a Go HTTP client library. Prior to version 0.6.4, a race condition vulnerability exists in the shared HTTP client configuration. The global `defaultClient` is mutated during request execution without synchronization, directly modifying the shared `http.Client`'s `Transport`, `Timeout`, and `CheckRedirect` properties. Impacted applications include that that use axios4go with concurrent requests (multiple goroutines, `GetAsync`, `PostAsync`, etc.), those where different requests use different proxy configurations, and those that handle sensitive data (authentication credentials, tokens, API keys). Version 0.6.4 fixes this issue. | |
| Title | axios4go's Race Condition in Shared HTTP Client Allows Proxy Configuration Leak | |
| Weaknesses | CWE-362 | |
| References |
| |
| Metrics |
cvssV4_0
|