Oxia: Bearer token exposed in debug log messages on authentication failure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| oxia-db | oxia | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Oxia-db | Oxia |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-pm7q-rjjx-979p | Oxia exposes bearer token in debug log messages on authentication failure |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.308% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Oxia-db
Oxia-db oxia |
|
| Vendors & Products |
Oxia-db
Oxia-db oxia |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Oxia is a metadata store and coordination system. Prior to 0.16.2, when OIDC authentication fails, the full bearer token is logged at DEBUG level in plaintext. If debug logging is enabled in production, JWT tokens are exposed in application logs and any connected log aggregation system. This vulnerability is fixed in 0.16.2. | |
| Title | Oxia: Bearer token exposed in debug log messages on authentication failure | |
| Weaknesses | CWE-532 | |
| References |
| |
| Metrics |
cvssV4_0
|