It was reported  that Jenkins suffers from a vulnerability that allows an attacker with HTTP access to the server to retrieve the master cryptographic keys used by Jenkins to encrypt sensitive data in configuration files under $JENKINS_HOME, in HTML forms, the authenticate REST API access from users, and authenticating slaves connecting to the master. An attacker with this key could execute arbitrary code on the Jenkins master or impersonate arbitrary users via REST API calls.
This can be somewhat mitigated, depending on certain installations:
- this is only applicable on Jenkins instances that have slaves attached to them, and allow anonymous read access
- regenerated API tokens, with a user can regenerate, cannot be impersonated by the attacker
This is fixed upstream in version 1.498 and the LTS 1.480.2 version.
In git, the fix seems to be spread across a few commits
In git, the fix seems to be spread across a few commits (those prefixed with [SECURITY-49]):
This issue has been addressed in following products:
RHEL 6 Version of OpenShift Enterprise
Via RHSA-2013:0220 https://rhn.redhat.com/errata/RHSA-2013-0220.html