CVE-2020-2188: Enumeration of Credentials IDs in Amazon EC2 Plugin

org.jenkins-ci.plugins:ec2 Updated 02 Oct 2025

Summary

24/05/2022
Yes i
Moderate
4.3

CVE-2020-2188: Users with Overall/Read access can enumerate credentials IDs in Amazon EC2 Plugin. Affects org.jenkins-ci.plugins:ec2 versions < 1.50.2. Fixed in 1.50.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 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 Amazon EC2 Plugin is a plugin for Jenkins, an open-source automation server. It allows users to configure and manage Amazon EC2 instances as part of their Jenkins workflows. The plugin provides a list of applicable credentials IDs for users to select the appropriate credentials for their EC2 instances. This functionality is crucial for securely accessing and managing EC2 resources within Jenkins.

Vulnerability Detail

The vulnerability (CVE-2020-2188) in the Amazon EC2 Plugin versions 1.50.1 and earlier allows users with Overall/Read access to enumerate valid credentials IDs. This means that any user with the necessary permissions can obtain a list of valid credentials IDs, which can be exploited in combination with another vulnerability to capture the credentials. This vulnerability poses a moderate risk as it can potentially lead to unauthorized access to sensitive credentials and compromise the security of the EC2 instances managed by Jenkins.

How To Fix

Minimum fixed version

1.50.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 specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring that only trusted users have Overall/Read access in their Jenkins environment. Additionally, regular monitoring of access logs and suspicious activities can help detect any unauthorized attempts to enumerate credentials IDs.

Conclusion

The enumeration of credentials IDs vulnerability in Amazon EC2 Plugin versions 1.50.1 and earlier can allow unauthorized users to obtain valid credentials IDs, potentially leading to unauthorized access to EC2 instances and compromising the security of the Jenkins environment. It is crucial to upgrade to version 1.50.2 or later to fix this vulnerability and enhance the security of the EC2 instances managed by Jenkins. For further support and assistance in vulnerability remediation, please contact DevNack.com.

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

Share this vulnerability

FAQ

The vulnerability allows users with Overall/Read access to obtain a list of valid credentials IDs, which can be used to capture sensitive credentials. This can potentially lead to unauthorized access to EC2 instances and compromise the security of the Jenkins environment.

Users of Amazon EC2 Plugin versions 1.50.1 and earlier are affected by this vulnerability. Specifically, users with Overall/Read access permissions are at risk.

There are no known public exploits for this vulnerability at the time of this report. However, it is important to promptly upgrade to the fixed version to mitigate the risk.

No, this vulnerability requires authenticated access to the Jenkins environment with Overall/Read permission. It cannot be exploited remotely without valid credentials.

Yes, the CVSS score for this vulnerability is 4.3, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:ec2.

How To Fix

Minimum fixed version

1.50.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