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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade jenkins | Jun 21, 2019 | Apr 10, 2019 |
| Arch Linux | — | Upgrade to the latest version of Arch Linux | Jul 11, 2025 | Apr 10, 2019 |
| Jenkins 2019 04 10 | — | Upgrade Jenkins LTS to the latest versionUpgrade Jenkins to the latest versionUpgrade Jenkins LTS to version 2.164.2Upgrade Jenkins to version 2.172 | Apr 12, 2019 | Apr 10, 2019 |
| Redhat Openshift | — | Upgrade jenkinsUpgrade atomic-openshift-web-consoleUpgrade openshift-ansibleUpgrade golang-github-openshift-oauth-proxyUpgrade openshift-enterprise-autohealUpgrade atomic-openshift-metrics-serverUpgrade atomic-openshift-node-problem-detectorUpgrade atomic-openshift-service-idlerUpgrade atomic-openshift-deschedulerUpgrade jenkins-2-pluginsUpgrade atomic-openshift-cluster-autoscalerUpgrade atomic-enterprise-service-catalogUpgrade cri-oUpgrade golang-github-prometheus-alertmanagerUpgrade atomic-openshift-dockerregistryUpgrade openshift-enterprise-cluster-capacityUpgrade golang-github-prometheus-prometheusUpgrade golang-github-prometheus-node_exporter | Jul 4, 2019 | Apr 10, 2019 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub