First published: Wed Apr 10 2019(Updated: )
Users who cached their CLI authentication before Jenkins was updated to 2.150.2 and newer, or 2.160 and newer, would remain authenticated in Jenkins 2.171 and earlier and Jenkins LTS 2.164.1 and earlier, because the fix for CVE-2019-1003004 in these releases did not reject existing remoting-based CLI authentication caches.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Jenkins | <=2.164.1 | |
Jenkins Jenkins | <=2.171 | |
redhat openshift container platform | =3.11 | |
oracle communications Cloud native core automated test suite | =1.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-1003049 is a vulnerability that allows users who cached their CLI authentication before Jenkins was updated to remain authenticated in certain versions of Jenkins.
Jenkins versions 2.164.1 and earlier, as well as Jenkins LTS 2.164.1 and earlier, are affected by CVE-2019-1003049.
CVE-2019-1003049 has a severity rating of 8.1 (high).
To fix CVE-2019-1003049, users should update Jenkins to version 2.150.2 or newer, or version 2.160 or newer.
More information about CVE-2019-1003049 can be found at the following references: http://www.securityfocus.com/bid/107901, https://access.redhat.com/errata/RHBA-2019:1605, https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289