Tugtainer: OIDC id_token claims accepted without signature/audience/expiry verification
What fixes it
No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.
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.
Text from CVE List
Affected versions 2
- tugtaineraffected: < 1.31.3CVE List
- tugtainer, dockerized software<= 1.31.2GitHub