Tugtainer: OIDC login remains accessible when OIDC_ENABLED is false
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.598% 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.30.3, Tugtainer's OIDC authentication can still be initiated even when OIDC_ENABLED=false. The /auth/oidc/enabled endpoint correctly reports that OIDC is disabled. However, a direct request to /auth/oidc/login still starts the OIDC login flow, returns HTTP 302, sets an oidc_state cookie, and redirects the user to the configured OIDC authorization endpoint. This bypasses the intended OIDC disable switch. This issue has been patched in version 1.30.3. | |
| Title | Tugtainer: OIDC login remains accessible when OIDC_ENABLED is false | |
| Weaknesses | CWE-284 | |
| References |
| |
| Metrics |
cvssV3_1
|