AxonHub through 1.0.0-beta11 Privilege Escalation via Service Account API Key Scopes
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| looplj | AxonHub | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Looplj | Axonhub |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.410% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Looplj
Looplj axonhub |
|
| Vendors & Products |
Looplj
Looplj axonhub |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | AxonHub through 1.0.0-beta11 contains a privilege escalation vulnerability that allows project users to assign system-level scopes by creating service_account API keys with unvalidated scopes. Attackers holding write_api_keys can mint keys with read_channels and query /admin/graphql to read every channel's configuration, including base URLs and model lists. | |
| Title | AxonHub through 1.0.0-beta11 Privilege Escalation via Service Account API Key Scopes | |
| Weaknesses | CWE-266 | |
| References |
|
|
| Metrics |
cvssV3_1
|