Collins v2.1.0
Collins
Collins 2.1.0 has a very important security patch.
Collins has a feature that allows you to encrypt certain attributes on every asset. It also had a permission that restricted which users could read those encrypted tags. It did NOT have a permission that restricted which users could modify encrypted tags.
It is strongly recommended that you upgrade to collins 2.1.0 if you are using the encrypted tags feature, as well as rotate any values stored in encrypted tags.
The severity of this vulnerability depends heavily upon how you use collins in your infrastructure. If you do not use the encrypted tags feature, you are not vulnerable to this problem. If you do use the encrypted tags feature, you will need to explore your automation and consider how vulnerable you are.
If, for example, your infrastructure has automation that regularly sets the root password on servers to match a value that is in collins, an attacker without the ability to read the current password could set it to a value that they know, wait for the automation to change the password, and then gain root on a server.
This change is backwards compatible with collins v2.0.0, though once
you upgrade it will stop any writes to encrypted tags by users that have
not been granted feature.canWriteEncryptedTags permission. We have also renamed feature.canSeePasswords to feature.canSeeEncryptedTags, but collins will continue to respect the value of feature.canSeePasswords if feature.canSeeEncryptedTags is not set. Once feature.canSeeEncryptedTags is set, collins will ignore the value of feature.canSeePasswords.
See https://github.com/tumblr/collins/releases/tag/v2.1.0 for download links.
Please reach out to this email list, open an issue on github, ask on the IRC channel, or contact me directly (wi...@tumblr.com or primer_ in the IRC channel) if you have questions about this vulnerability, or if your instance of collins is vulnerable to attack.