CVE-2013-0158: Low severity jenkins vulnerability
It was reported [1] 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 $JENKINSHOME, 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
[1] https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04
In git, the fix seems to be spread across a few commits (those prefixed with [SECURITY-49]):
https://github.com/jenkinsci/jenkins/commit/a9aff088f327278a8873aef47fa8f80d3c5932fd https://github.com/jenkinsci/jenkins/commit/4895eaafca468b7f0f1a3166b2fca7414f0d5da5 https://github.com/jenkinsci/jenkins/commit/c3d8e05a1b3d58b6c4dcff97394cb3a79608b4b2 https://github.com/jenkinsci/jenkins/commit/3dc13b957b14cec649036e8dd517f0f9cb21fb04 https://github.com/jenkinsci/jenkins/commit/94a8789b699132dd706021a6be1b78bc47f19602
Other sources
Unspecified vulnerability in Jenkins before 1.498, Jenkins LTS before 1.480.2, and Jenkins Enterprise 1.447.x before 1.447.6.1 and 1.466.x before 1.466.12.1, when a slave is attached and anonymous read access is enabled, allows remote attackers to obtain the master cryptographic key via unknown vectors.
— GitHub
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2013-0158?
CVE-2013-0158 has a severity rating that can vary but is generally considered a high-risk vulnerability due to the exposure of master cryptographic keys.
How do I fix CVE-2013-0158?
To fix CVE-2013-0158, upgrade Jenkins to version 1.480.2 or later, or to version 1.498 if you have version 1.481 or newer.
What types of systems are affected by CVE-2013-0158?
CVE-2013-0158 affects multiple versions of Jenkins and Cloudbees Jenkins, specifically versions prior to 1.480.2.
How can an attacker exploit CVE-2013-0158?
An attacker can exploit CVE-2013-0158 by gaining HTTP access to the Jenkins server, allowing them to retrieve sensitive master cryptographic keys.
What data is compromised in CVE-2013-0158?
CVE-2013-0158 compromises the master cryptographic keys used by Jenkins to encrypt sensitive data in configuration files.