[<prev] [next>] [day] [month] [year] [list]
Message-Id: <EC0A18B5-C79C-4A80-9A64-A9F143E90E75@beckweb.net>
Date: Wed, 10 Apr 2019 17:05:37 +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.172
* Jenkins LTS 2.164.2
Summaries of the vulnerabilities are below. More details, severity, and
attribution can be found here:
https://jenkins.io/security/advisory/2019-04-10/
We provide advance notification for security updates on this mailing list:
https://groups.google.com/d/forum/jenkinsci-advisories
If you discover security vulnerabilities in Jenkins, please report them as
described here:
https://jenkins.io/security/#reporting-vulnerabilities
---
SECURITY-1289 / CVE-2019-1003049
The fix for SECURITY-901 in Jenkins 2.150.2 and 2.160 did not reject
existing remoting-based CLI authentication caches.
This means that users who cached their CLI authentication before Jenkins was
updated to 2.150.2 and newer, or 2.160 and newer, would remain authenticated.
Support for the remoting-based CLI was dropped in Jenkins 2.165, so newer
weekly releases are not affected.
SECURITY-1327 / CVE-2019-1003050
The f:validateButton form control for the Jenkins UI did not properly escape
job URLs. This resulted in a cross-site scripting (XSS) vulnerability
exploitable by users with the ability to control job names.
Powered by blists - more mailing lists
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.
