Impact
Yeti does not account for empty SECRET_KEY
variables when generating cryptographic secrets for authentication, enabling attackers to forge valid JWTs for authentication.
https://github.com/yeti-platform/yeti-docker, prior to 4a67458c9dcf348951e4d921e5c5af28b33cee9e, would set the key to SECRET
. Implications that this should be changed may not have been clear to the users.
Patches
Version 2.1.12 fixes this, versions prior to this are vulnerable.
Workarounds
Ensure the SECRET_KEY
environment variable or config option is set randomly.
References
Fix: #1142
Impact
Yeti does not account for empty
SECRET_KEY
variables when generating cryptographic secrets for authentication, enabling attackers to forge valid JWTs for authentication.https://github.com/yeti-platform/yeti-docker, prior to 4a67458c9dcf348951e4d921e5c5af28b33cee9e, would set the key to
SECRET
. Implications that this should be changed may not have been clear to the users.Patches
Version 2.1.12 fixes this, versions prior to this are vulnerable.
Workarounds
Ensure the
SECRET_KEY
environment variable or config option is set randomly.References
Fix: #1142