Approved changes feed: RSS · Atom
cpe:2.3:a:travis-ci:travis_ci:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Travis Ci (1b00131d-df3c-572d-9cab-726cc0a3801e) |
|---|---|
| Product | Travis Ci (9370cbce-4a28-5317-97a7-0bf755bda56f) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-41077 |
vulnerable | 2026-06-08 05:35:19.615618 |
Details available
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.
Published: 2021-09-14T15:07:31.000Z
Updated: 2024-08-04T02:59:31.014Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.