Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Quenary | tugtainer | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Quenary | Tugtainer |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.338% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Quenary
Quenary tugtainer |
|
| Vendors & Products |
Quenary
Quenary tugtainer |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.31.3, when the OIDC login flow completes, backend/modules/auth/providers/auth_oidc_provider.py decodes the id_token returned by the identity provider's token endpoint using jose.jwt.get_unverified_claims() instead of jwt.decode(). This skips signature verification, audience (aud) validation, issuer (iss) validation, and expiry (exp) checking entirely. The extracted claims (email/sub/preferred_username) are then used directly as the user_id for the resulting Tugtainer session. This issue has been patched in version 1.31.3. | |
| Title | Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|