Amazon Ec2Application · Jenkins
CVE-2020-2090
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA cross-site request forgery vulnerability in Jenkins Amazon EC2 Plugin 1.47 and earlier allows attackers to connect to an attacker-specified URL within the AWS region using attacker-specified credentials IDs obtained through another method.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA CSRF vulnerability in Jenkins Amazon EC2 Plugin 1.47 and earlier allows authenticated attackers to trigger connections to attacker-specified URLs within AWS using attacker-specified credentials IDs, enabling unauthorized AWS resource access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Amazon Ec2Application
<= 1.47CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Amazon EC2 Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Amazon EC2' or check the plugin manifest file in $JENKINS_HOME/plugins/amazon-ec2/Affected if The plugin appears in the installed plugins list
-
Determine the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the Amazon EC2 plugin and note the version number displayedAffected if The version is 1.47 or earlier
-
Verify AWS credentials are configuredNavigate to Jenkins > Manage Jenkins > Configure Clouds > Amazon EC2 and check if any AWS credentials are added in the plugin configurationAffected if AWS credentials (IAM access keys or via IAM role) are configured for the EC2 cloud plugin
-
Check EC2 cloud configuration existsNavigate to Jenkins > Manage Jenkins > Configure Clouds and look for Amazon EC2 cloud configuration entries with specified AMI IDs and instance settingsAffected if An Amazon EC2 cloud is configured with AMI details and instance launch settings
-
Confirm Jenkins user permissions are broadReview Jenkins > Manage Jenkins > Manage Users and check user/role permissions in Configure Global Security, focusing on who has Overall/Read and Credentials/Use permissionsAffected if Multiple users or groups have permissions beyond the minimum required, especially with credentials access
You are affected if the Amazon EC2 Plugin version is 1.47 or earlier AND you have AWS credentials configured in the plugin, regardless of whether the EC2 cloud is actively used.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins Amazon EC2 Plugin to version 1.48 or later which includes CSRF protection. Review and restrict Jenkins user permissions to minimize attack surface.
Fix this in Amazon Ec2
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2090 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2090 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data