Collins v2.2.0 Release Notes

Release Date: 2017-10-11 // over 6 years ago
  • ๐Ÿ”’ This version of Collins includes an important security patch, as well as several new features and bug fixes.

    ๐Ÿ”’ The security patch is adding CSRF protection to the various forms of the Collins web UI. Currently, if an attacker can guess (or bruteforce) the asset tags of nodes he or she would be able to create assets, decommission assets, put assets in maintenance, etc. by getting a logged in user to visit a webpage. More information can be found in the pull request (#560).

    ๐Ÿš€ Here is the full list of merged pull request since the last release. Many thanks to everyone who contributed!

Previous changes from v2.1.0

  • ๐Ÿ”’ 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.

    • ๐Ÿ— Ensure that we build only with java 1.7 #473 @Primer42
    • Write encrypted tags permission #486 @Primer42