Описание
Insufficient Session Expiration in Jenkins
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2019-1003049
- https://github.com/jenkinsci/jenkins/commit/0eeaa087aac192fb39f52928be5a5bbf16627ea6
- https://access.redhat.com/errata/RHBA-2019:1605
- https://jenkins.io/security/advisory/2019-04-10/#SECURITY-1289
- https://www.oracle.com/security-alerts/cpuapr2022.html
- http://www.securityfocus.com/bid/107901
Пакеты
org.jenkins-ci.main:jenkins-core
<= 2.164.1
2.164.2
org.jenkins-ci.main:jenkins-core
>= 2.165, <= 2.171
2.172
Связанные уязвимости
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.
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.
Users who cached their CLI authentication before Jenkins was updated t ...