Personal access token delete filters on Session columns while deleting from PersonalAccessTokenDB
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Ericsson | CodeChecker | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Ericsson | Codechecker |
|
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.300% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Ericsson
Ericsson codechecker |
|
| Vendors & Products |
Ericsson
Ericsson codechecker |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The personal access token removal query selects from PersonalAccessTokenDB but filters on columns of Session, with no join between them. SQLAlchemy resolves that as an implicit cross join, so the filter does not constrain the delete to the calling user's own token in the way the code reads as intending. This way a user can delete all personal access tokens in the system. | |
| Title | Personal access token delete filters on Session columns while deleting from PersonalAccessTokenDB | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV4_0
|