Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Oct 2017 18:21:48 +0200
From: Daniel Beck <ml@...kweb.net>
To: oss-security@...ts.openwall.com
Subject: Multiple vulnerabilities in Jenkins

Jenkins is an open source automation server which enables developers around 
the world to reliably build, test, and deploy their software. The following 
releases contain fixes for security vulnerabilities:

* Jenkins (weekly) 2.84
* Jenkins (LTS) 2.73.2

Summaries of the vulnerabilities are below. More details, severity, and
attribution can be found here:
https://jenkins.io/security/advisory/2017-10-11/

We provide advance notification for security updates on this mailing list:
https://groups.google.com/d/forum/jenkinsci-advisories

If you find security vulnerabilities in Jenkins, please report them as
described here:
https://jenkins.io/security/#reporting-vulnerabilities

---

SECURITY-478
Users with permission to create or configure agents in Jenkins could 
configure a launch method called Launch agent via execution of command on 
master. This allowed them to run arbitrary shell commands on the master 
node whenever the agent was supposed to be launched.

SECURITY-514
Information about Jenkins user accounts is generally available to anyone 
with Overall/Read permissions via the /user/(username)/api remote API. This 
included e.g. Jenkins users' email addresses if the Mailer Plugin is 
installed.

SECURITY-555
Jenkins bundled a version of the commons-httpclient library with the 
vulnerability CVE-2012-6153 that incorrectly verified SSL certificates, 
making it susceptible to man-in-the-middle attacks.

SECURITY-611
The remote API at /computer/(agent-name)/api showed information about tasks 
(typically builds) currently running on that agent. This included 
information about tasks that the current user otherwise has no access to, 
e.g. due to lack of Job/Read permission.

SECURITY-618
The remote API at /queue/item/(ID)/api showed information about tasks in 
the queue (typically builds waiting to start). This included information 
about tasks that the current user otherwise has no access to, e.g. due to 
lack of Job/Read permission.

SECURITY-617
The remote API at /job/(job-name)/api contained information about upstream 
and downstream projects. This included information about tasks that the 
current user otherwise has no access to, e.g. due to lack of Job/Read 
permission.

SECURITY-616
The Jenkins default form control for passwords and other secrets, 
<f:password/>, supports form validation (e.g. for API keys). The form 
validation AJAX requests were sent via GET, which could result in secrets 
being logged to a HTTP access log in non-default configurations of 
Jenkins, and made available to users with access to these log files.

Powered by blists - more mailing lists

Your e-mail address:

Please check out the Open Source Software Security Wiki, which is counterpart to this mailing list.

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.