Jenkins 2.213 and earlier, LTS 2.204.1 and earlier improperly reuses encryption key parameters in the Inbound TCP Agent Protocol/3, allowing unauthorized attackers with knowledge of agent names to obtain the connection secrets for those agents, which can be used to connect to Jenkins, impersonating those agents.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Freebsd | — | Upgrade jenkinsUpgrade jenkins-lts | Jan 30, 2020 | Jan 29, 2020 |
| Jenkins 2020 01 29 | — | Upgrade Jenkins LTS to version 2.204.2Upgrade Jenkins to the latest versionUpgrade Jenkins LTS to the latest versionUpgrade Jenkins to version 2.219 | Jan 30, 2020 | Jan 29, 2020 |
| Redhat Openshift | — | Upgrade atomic-openshift-web-consoleUpgrade openshift-kuryrUpgrade cri-oUpgrade atomic-openshift-node-problem-detectorUpgrade atomic-openshiftUpgrade golang-github-openshift-oauth-proxyUpgrade openshift-ansibleUpgrade openshift-enterprise-cluster-capacityUpgrade golang-github-prometheus-prometheusUpgrade atomic-openshift-deschedulerUpgrade golang-github-prometheus-alertmanagerUpgrade jenkins-2-pluginsUpgrade openshift-enterprise-autohealUpgrade atomic-openshift-service-idlerUpgrade golang-github-prometheus-node_exporterUpgrade atomic-openshift-metrics-serverUpgrade atomic-openshift-dockerregistryUpgrade atomic-openshift-cluster-autoscalerUpgrade atomic-enterprise-service-catalogUpgrade jenkins | Mar 18, 2020 | Jan 29, 2020 |
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