CVE-2019-10470: Jenkins Kubernetes CI/CD Plugin Credential Enumeration Vulnerability
Summary
CVE-2019-10470: Jenkins Kubernetes CI/CD Plugin vulnerable to Credential Enumeration. Affects com.elasticbox.jenkins-ci.plugins:kubernetes-ci versions < 1.3. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins Kubernetes CI/CD Plugin is a plugin for the Jenkins automation server that allows users to deploy and manage applications on Kubernetes clusters. It integrates Jenkins with Kubernetes, enabling users to build, test, and deploy their applications using Jenkins pipelines. The plugin provides functionality for managing credentials, such as API tokens and SSH keys, which are used for authentication and authorization when interacting with Kubernetes clusters.
Vulnerability Detail
A missing permission check in the Jenkins ElasticBox Jenkins Kubernetes CI/CD Plugin allowed users with Overall/Read access to enumerate credentials stored in Jenkins. This means that an attacker with the appropriate permissions could retrieve the IDs of credentials stored in Jenkins, potentially leading to further attacks or unauthorized access to sensitive information. The vulnerability has a CVSS score of 6.5, indicating a moderate severity.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As Jenkins has suspended distribution of the vulnerable plugin, there is no official workaround provided. However, users can consider removing the plugin from their Jenkins installation and exploring alternative solutions for managing Kubernetes deployments.
Conclusion
The Jenkins Kubernetes CI/CD Plugin is vulnerable to credential enumeration, allowing users with Overall/Read access to retrieve the IDs of credentials stored in Jenkins. As Jenkins has suspended distribution of this plugin, it is advisable to remove the plugin from the Jenkins installation and explore alternative solutions for managing Kubernetes deployments. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for com.elasticbox.jenkins-ci.plugins:kubernetes-ci →
FAQ
The vulnerability allows users with Overall/Read access to enumerate credentials stored in Jenkins, potentially leading to unauthorized access to sensitive information or further attacks.
No, as Jenkins has suspended distribution of the vulnerable plugin, there is no official patch available. It is recommended to find an alternative plugin or solution for managing Kubernetes deployments in Jenkins.
No, this vulnerability requires users to have Overall/Read access to Jenkins in order to enumerate credentials. Remote exploitation is not possible unless an attacker already has the necessary access.
As Jenkins has suspended distribution of the vulnerable plugin, the best mitigation is to remove the plugin from the Jenkins installation and explore alternative solutions for managing Kubernetes deployments.
There is no specific evidence of this vulnerability being exploited in the wild. However, it is always recommended to apply security updates and take necessary precautions to protect against potential attacks.
Related vulnerabilities
Recent vulnerabilities recorded for com.elasticbox.jenkins-ci.plugins:kubernetes-ci.
