Repository compromise via comment-triggered privileged workflow
Published Apr 6, 2021 · Updated Aug 3, 2024
Improper workflow authorization in Amazon Web Services Projen 0.6.0 through 0.16.40 allows remote authenticated users to execute code. The NodeProject rebuild-bot workflow accepts an issue_comment containing @projen rebuild and runs pull-request content with the target repository's GITHUB_TOKEN. Any GitHub user can reach it; repositories without default-branch protection expose configured secrets and allow repository changes.
Summary
What happened
Improper workflow authorization in Amazon Web Services Projen 0.6.0 through 0.16.40 allows remote authenticated users to execute code. The NodeProject rebuild-bot workflow accepts an issue_comment containing @projen rebuild and runs pull-request content with the target repository's GITHUB_TOKEN. Any GitHub user can reach it; repositories without default-branch protection expose configured secrets and allow repository changes.
The record
- CVE
- CVE-2021-21423
- Published
- Apr 6, 2021
- Updated
- Aug 3, 2024
- Vendor
- Amazon Web Services
- Product
- Projen
- Classifications
- CWE-527, T1195.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 6, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.6.0, < 0.16.41
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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