First published: Thu Mar 18 2021(Updated: )
CloudBees AWS Credentials Plugin 1.28 and earlier does not perform a permission check in a helper method for HTTP endpoints. This allows attackers with Overall/Read permission to enumerate credentials IDs of AWS credentials stored in Jenkins if any of the following plugins are installed: - [Amazon Elastic Container Service (ECS) / Fargate](https://plugins.jenkins.io/amazon-ecs) - [AWS Parameter Store Build Wrapper](https://plugins.jenkins.io/aws-parameter-store) - [AWS SAM](https://plugins.jenkins.io/aws-sam)\n\nFurther plugins may use this helper method as well without performing a permission check themselves. Credentials IDs obtained this way can be used as part of an attack to capture the credentials using another vulnerability. CloudBees AWS Credentials Plugin 1.28.1 performs permission checks in the helper method for HTTP endpoints.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
<=1.28 | ||
Jenkins Cloudbees Aws Credentials | <=1.28 | |
maven/org.jenkins-ci.plugins:aws-credentials | <=1.28 | 1.28.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-21625 has a medium severity rating due to the potential for credential ID enumeration.
To fix CVE-2021-21625, upgrade the Jenkins CloudBees AWS Credentials Plugin to version 1.28.1 or later.
Anyone using CloudBees AWS Credentials Plugin version 1.28 or earlier is affected by CVE-2021-21625.
No, attackers need Overall/Read permission to exploit CVE-2021-21625.
CVE-2021-21625 can allow attackers to enumerate AWS credentials IDs stored in Jenkins.