CVE-2021-41077
Summary
| CVE | CVE-2021-41077 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-09-14 16:15:00 UTC |
| Updated | 2021-09-29 18:37:00 UTC |
| Description | 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. |
Risk And Classification
Problem Types: CWE-862
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| JavaScript is not available. | MISC | twitter.com | |
| The Travis CI Blog: Security Bulletin | MISC | blog.travis-ci.com | |
| Travis CI Leaked Secure Environment Variables | Hacker News | MISC | news.ycombinator.com | |
| Security Bulletin - Announcements - Travis CI Community | MISC | travis-ci.community | |
| Péter Szilágyi (karalabe.eth) on Twitter: "Between the 3 Sept and 10 Sept, secure env vars of *all* public @travisci repositories were injected into PR builds. Signing keys, access creds, API tokens. Anyone could exfiltrate these and gain lateral movement into 1000s of orgs. #security 1/4 https://t.co/i23jFzAjjH" | MISC | twitter.com | |
| Secure env vars of all public travisci repositories were injected into PR builds | Hacker News | MISC | news.ycombinator.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.