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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
None
No privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
Low
Partial disruption
CVSS Vector v3.1
Weakness Type (CWE)
References 3
https://github.com/Quenary/tugtainer/commit/76371db679334b002d4af544b0f3b8587ad…
security-advisories@github.com
https://github.com/Quenary/tugtainer/releases/tag/v1.30.3
security-advisories@github.com
https://github.com/Quenary/tugtainer/security/advisories/GHSA-rg7c-vpfp-2w43
security-advisories@github.com