CVE-2020-2168: RCE vulnerability in Jenkins Azure Container Service Plugin

Summary

24/05/2022
Yes i
High
8.8

CVE-2020-2168: RCE vulnerability in Jenkins Azure Container Service Plugin. Affects org.jenkins-ci.plugins:azure-acs versions < 1.0.2. Fixed in 1.0.2. 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 Your last release was probably never penetration tested 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 Azure Container Service Plugin is a Maven package that provides integration between Jenkins and Azure Container Service. It allows users to build, deploy, and manage containers on Azure. The plugin enables seamless integration with Azure Container Service, providing a convenient way to automate container-based workflows within Jenkins.

Vulnerability Detail

The Azure Container Service Plugin version 1.0.1 and earlier is vulnerable to a remote code execution (RCE) attack. The plugin does not properly configure its YAML parser, allowing the instantiation of arbitrary types. This vulnerability can be exploited by users who can provide YAML input files to the plugin's build step. An attacker could craft a malicious YAML file that, when processed by the plugin, executes arbitrary code on the Jenkins server. This could lead to unauthorized access, data breaches, or further compromise of the Jenkins environment. The vulnerability has a CVSS score of 8.8, indicating a high severity level.

How To Fix

Minimum fixed version

1.0.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of the Azure Container Service Plugin to mitigate the risk of exploitation.

Conclusion

The Azure Container Service Plugin version 1.0.1 and earlier is vulnerable to a remote code execution (RCE) attack. It is crucial to upgrade to version 1.0.2 or later to mitigate the risk of exploitation. This upgrade ensures that the YAML parser is properly configured to prevent the instantiation of arbitrary types, enhancing the security of container workflows in Jenkins. For further support and guidance, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:azure-acs →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary code on the Jenkins server, potentially leading to unauthorized access, data breaches, or further compromise of the Jenkins environment.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the pom.xml file to provide accurate vulnerability information.

Yes, this vulnerability has a CVSS score of 8.8, indicating a high severity level.

There are no known public exploits for this vulnerability at the time of this report. However, it is crucial to apply the recommended fix to prevent potential exploitation.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.

How To Fix

Minimum fixed version

1.0.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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