Secret disclosure via forked pull request builds
Published Sep 14, 2021 · Updated Aug 4, 2024
Information disclosure in Travis CI builds dated September 3 through September 10, 2021 allows remote attackers to read repository secrets. The activation process makes protected environment data available to fork-originated pull-request builds, allowing build code to print files containing the secrets. Exposure requires a fork of a public repository and a build that prints affected files; private repositories and unforked public repositories are not affected.
Summary
What happened
Information disclosure in Travis CI builds dated September 3 through September 10, 2021 allows remote attackers to read repository secrets. The activation process makes protected environment data available to fork-originated pull-request builds, allowing build code to print files containing the secrets. Exposure requires a fork of a public repository and a build that prints affected files; private repositories and unforked public repositories are not affected.
The record
- CVE
- CVE-2021-41077
- Published
- Sep 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-862, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo