CVE-2020-2309: Missing authorization in Jenkins Kubernetes Plugin

Summary

24/05/2022
Yes i
Moderate
4.3

CVE-2020-2309: Missing authorization in Jenkins Kubernetes Plugin. Affects org.csanchez.jenkins.plugins:kubernetes across 4 version ranges.

< 1.21.6 >= 1.22.0, < 1.25.4.1 >= 1.26.0, < 1.26.5 >= 1.27.0, < 1.27.4

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Kubernetes Plugin is a Maven package (org.csanchez.jenkins.plugins:kubernetes) that integrates Jenkins with Kubernetes, allowing users to dynamically provision Jenkins agents on Kubernetes clusters. It provides a scalable and efficient way to run Jenkins builds and deployments. However, versions prior to 1.27.4, 1.26.5, 1.25.4.1, and 1.21.6 of the plugin have a vulnerability that allows attackers with Overall/Read permission to enumerate credentials IDs stored in Jenkins. This enumeration can be used as part of an attack to capture the credentials using another vulnerability.

Vulnerability Detail

The vulnerability in the Jenkins Kubernetes Plugin arises from a missing authorization check in an HTTP endpoint. This means that an attacker with Overall/Read permission can exploit this vulnerability to enumerate credentials IDs of credentials stored in Jenkins. By obtaining these credentials IDs, an attacker can potentially gain unauthorized access to sensitive information or perform malicious actions. The vulnerability has a CVSS score of 4.3, indicating a moderate severity level.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.21.6 1.21.6
  • >= 1.22.0, < 1.25.4.1 1.25.4.1
  • >= 1.26.0, < 1.26.5 1.26.5
  • >= 1.27.0, < 1.27.4 1.27.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. However, users can mitigate the risk by ensuring that only trusted users have Overall/Read permission in Jenkins. Additionally, it is crucial to keep the Jenkins Kubernetes Plugin up to date with the latest security patches.

Conclusion

The Jenkins Kubernetes Plugin prior to versions 1.27.4, 1.26.5, 1.25.4.1, and 1.21.6 has a vulnerability that allows attackers with Overall/Read permission to enumerate credentials IDs stored in Jenkins. This can lead to unauthorized access to sensitive information or malicious actions. It is crucial to upgrade to the fixed versions of the plugin and ensure that only trusted users have the necessary permissions in Jenkins. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for org.csanchez.jenkins.plugins:kubernetes →

Share this vulnerability

FAQ

The vulnerability allows attackers with Overall/Read permission to enumerate credentials IDs stored in Jenkins, potentially leading to unauthorized access to sensitive information or malicious actions.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your Jenkins instance is affected by this vulnerability. Simply provide your pom.xml file, and Vulert will analyze it in real-time and alert you if any open-source vulnerabilities, including this one, are detected.

There are currently no known exploits for this vulnerability. However, it is essential to apply the recommended fix to prevent potential exploitation.

While upgrading to the fixed versions of the Jenkins Kubernetes Plugin is the recommended approach, you can mitigate the risk by ensuring that only trusted users have Overall/Read permission in Jenkins and regularly monitoring for any unauthorized activities.

You can find more information about this vulnerability, including its technical details and the fixed versions of the Jenkins Kubernetes Plugin, in the advisory on the GitHub Advisory Database: [link to advisory]

Related vulnerabilities

Recent vulnerabilities recorded for org.csanchez.jenkins.plugins:kubernetes.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 1.21.6 1.21.6
  • >= 1.22.0, < 1.25.4.1 1.25.4.1
  • >= 1.26.0, < 1.26.5 1.26.5
  • >= 1.27.0, < 1.27.4 1.27.4

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback