Quenary Tugtainer
Tugtainer: OIDC login remains accessible when OIDC_ENABLED is false
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.
First public PoC
None yetno public PoC found
Public PoCs00 on GitHub
CVSS9.4critical · scored by CNA · CWE-284
CISA KEV
Not listednot known exploited
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
Quenary tugtainer
- < 1.30.3
Fixed in 1.30.3
Mitigation
Upgrade tugtainer to 1.30.3 or later.
References
- Vendor advisory github.com/Quenary/tugtainer/security/advisori…
- Patch github.com/Quenary/tugtainer/commit/76371db679…
- Release notes github.com/Quenary/tugtainer/releases/tag/v1.3…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.