[org.jenkins-ci.plugins:aws-credentials] Missing permission checks in Jenkins CloudBees AWS Credentials Plugin allows enumerating credentials IDs

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
• AWS Parameter Store Build Wrapper
• 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.

References

• https://nvd.nist.gov/vuln/detail/CVE-2021-21625
• https://www.jenkins.io/security/advisory/2021-03-18/#SECURITY-2032
• http://www.openwall.com/lists/oss-security/2021/03/18/5
• https://github.com/advisories/GHSA-jwr9-h4jm-c9ch