The activation process in Travis CI, for certain 2021-09-03 through 2021-09-10 builds, causes secret data to have unexpected sharing that is not specified by the customer-controlled .travis.yml file. In particular, the desired behavior (if .travis.yml has been created locally by a customer, and added to git) is for a Travis service to perform builds in a way that prevents public access to customer-specific secret environment data such as signing keys, access credentials, and API tokens. However, during the stated 8-day interval, secret data could be revealed to an unauthorized actor who forked a public repository and printed files during a build process.
References
Link | Resource |
---|---|
https://blog.travis-ci.com/2021-09-13-bulletin | Vendor Advisory |
https://twitter.com/peter_szilagyi/status/1437649838477283330 | Third Party Advisory |
https://news.ycombinator.com/item?id=28523350 | Third Party Advisory |
https://twitter.com/peter_szilagyi/status/1437646118700175360 | Third Party Advisory |
https://news.ycombinator.com/item?id=28524727 | Third Party Advisory |
https://travis-ci.community/t/security-bulletin/12081 | Vendor Advisory |
Configurations
Information
Published : 2021-09-14 09:15
Updated : 2021-09-29 11:37
NVD link : CVE-2021-41077
Mitre link : CVE-2021-41077
JSON object : View
CWE
CWE-862
Missing Authorization
Products Affected
travis-ci
- travis_ci