Security Advisories » Jenkins Security Advisory 2017-11-08
This advisory announces vulnerabilities in the following Jenkins deliverables:
Jenkins stores metadata related to people, which encompasses actual user accounts, as well as users appearing in SCM, in directories corresponding to the user ID on disk. These directories used the user ID for their name without additional escaping. This potentially resulted in a number of problems, such as the following:
User names consisting of a single forward slash would have their user record stored in the parent directory; deleting this user deleted all user records.
User names containing character sequences such as
.. could be used to clobber other configuration files in Jenkins.
User names could consist of reserved names such as
COM (on Windows).
This is not limited to the Jenkins user database security realm, other security realms such as LDAP may allow users to create user names that result in problems in Jenkins.
User names are now transformed into a filesystem-safe representation that is used as directory name.
Autocompletion suggestions for text fields were not escaped, resulting in a persisted cross-site scripting vulnerability if the source for the suggestions allowed specifying text that includes HTML metacharacters like less-than and greater-than characters.
Known previously unsafe sources for these suggestions include the names of loggers in the log recorder condition, and agent labels.
Autocompletion suggestions are now escaped and can no longer contain HTML-based formatting.
These versions include fixes to the vulnerabilities described above. All prior versions are considered to be affected by these vulnerabilities unless otherwise indicated.
The Jenkins project would like to thank the reporters for discovering and reporting these vulnerabilities: