CVE-2021-21423: Projen Rebuild-bot Workflow May Allow Unauthorised Vulnerability

HIGH
Advisory Identifier: GHSA-gg2g-m5wc-vccq
CVSS 6.8
CWE-527
Published
Advisory Summary

CVE-2021-21423 is a HIGH (CVSS 6.8) rebuild-bot workflow may allow unauthorised vulnerability (CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere) affecting Projen libraries in the npm ecosystem. The issue involves rebuild-bot workflow may allow unauthorised repository modifications. Remediation is available by upgrading affected packages to version 0.16.41.

CVE-2021-21423 at a Glance

CVE Identifier CVE-2021-21423
GHSA Identifier GHSA-gg2g-m5wc-vccq
Severity HIGH
CVSS v3.1 Base Score 6.8
CWE Classification CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere
Affected Product Projen
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 6.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2021-21423

To remediate this vulnerability, upgrade all affected Projen dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

projen fixed: 0.16.41
npm install projen@0.16.41
projen fixed: 0.16.41
pip install projen>=0.16.41
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls projen

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2021-21423, inspect your project dependencies using npm:

npm ls projen

Analyze the terminal output to locate any version of Projen in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.16.41), your application is affected.

Note: The npm ls projen command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere, where the product stores a cvs, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors. In Projen, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact `projen` is a project generation tool that synthesizes project configuration files such as `package.json`, `tsconfig.json`, `.gitignore`, GitHub Workflows, `eslint`, `jest`, and more, from a well-typed definition written in JavaScript. Users of projen's `NodeProject` project type (including any project type derived from it) include a `.github/workflows/rebuild-bot.yml` workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the "main" repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the "main" repository. The rebuild-bot workflow is triggered by comments including `@projen rebuild` on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an `issue_comment` event, and thus always executes with a `GITHUB_TOKEN` belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by `pull_request` events, which always execute with a `GITHUB_TOKEN` belonging to the repository from which the pull-request is made). Repositories that do not have branch protection configured on their default branch (typically `main` or `master`) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed `GITHUB_TOKEN` would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch. ### Patches The issue was mitigated in version `0.16.41` of the `projen` tool, which removes the `issue_comment` trigger from this workflow. Version `0.17.0` of projen completely removes the `rebuild-bot.yml` workflow. ### Workarounds The recommended way to address the vulnerability is to upgrade `projen`. Users who cannot upgrade `projen` may also remove the `.github/workflows/rebuild-bot.yml` file and add it to their `.gitignore` file (via `projenrc.js`) to mitigate the issue. ### References The `rebuild-bot.yml` workflow managed by `projen` is only one occurrence of a GitHub Workflows mis-configuration, but it may also be present in other workflows not managed by `projen` (either hand-written, or managed by other tools). For more information on this class of issues, the [Keeping your GitHub Actions and workflows secure: Preventing pwn requests][1] article provides a great overview of the problem. [1]: https://securitylab.github.com/research/github-actions-preventing-pwn-requests

CVE-2021-21423 Affected Projen Versions

2 component(s)
Fixed Versions:
0.16.41
Product / Package Ecosystem Affected Versions Fixed Version
projen
npm
≥ 0.6.0
< 0.16.41
0.16.41
projen
PyPI
< 0.16.41
0.16.41

References

Frequently Asked Questions

What is CVE-2021-21423?
CVE-2021-21423 is a security vulnerability in Projen involving Rebuild-bot workflow may allow unauthorised repository modifications under CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere.
Which Projen versions are affected?
Affected versions include releases prior to 0.16.41 across affected packages: projen.
What version fixes CVE-2021-21423?
Upgrading to 0.16.41 (or the latest patched release for your respective branch) resolves the vulnerability.
Is projen affected?
Yes, projen is affected in releases prior to 0.16.41. Upgrade your dependency to 0.16.41 or later.
What is the CVSS score of CVE-2021-21423?
CVE-2021-21423 has a CVSS v3.1 base score of 6.8 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N.
What CWE is associated with CVE-2021-21423?
CVE-2021-21423 is classified under CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere (The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.).
How can I check npm dependencies for CVE-2021-21423?
Run the dependency tree command: 'npm ls projen'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-gg2g-m5wc-vccq",
  "modified" : "2024-10-21T20:05:47Z",
  "published" : "2021-04-06T18:36:40Z",
  "aliases" : [ "CVE-2021-21423" ],
  "summary" : "Rebuild-bot workflow may allow unauthorised repository modifications",
  "details" : "### Impact\n\n`projen` is a project generation tool that synthesizes project configuration files such as `package.json`, `tsconfig.json`, `.gitignore`, GitHub Workflows, `eslint`, `jest`, and more, from a well-typed definition written in JavaScript. Users of projen's `NodeProject` project type (including any project type derived from it) include a `.github/workflows/rebuild-bot.yml` workflow that may allow any GitHub user to trigger execution of un-trusted code in the context of the \"main\" repository (as opposed to that of a fork). In some situations, such untrusted code may potentially be able to commit to the \"main\" repository.\n\nThe rebuild-bot workflow is triggered by comments including `@projen rebuild` on pull-request to trigger a re-build of the projen project, and updating the pull request with the updated files. This workflow is triggered by an `issue_comment` event, and thus always executes with a `GITHUB_TOKEN` belonging to the repository into which the pull-request is made (this is in contrast with workflows triggered by `pull_request` events, which always execute with a `GITHUB_TOKEN` belonging to the repository from which the pull-request is made).\n\nRepositories that do not have branch protection configured on their default branch (typically `main` or `master`) could possibly allow an untrusted user to gain access to secrets configured on the repository (such as NPM tokens, etc). Branch protection prohibits this escalation, as the managed `GITHUB_TOKEN` would not be able to modify the contents of a protected branch and affected workflows must be defined on the default branch. \n\n### Patches\n\nThe issue was mitigated in version `0.16.41` of the `projen` tool, which removes the `issue_comment` trigger from this workflow. Version `0.17.0` of projen completely removes the `rebuild-bot.yml` workflow.\n\n### Workarounds\n\nThe recommended way to address the vulnerability is to upgrade `projen`. Users who cannot upgrade `projen` may also remove the `.github/workflows/rebuild-bot.yml` file and add it to their `.gitignore` file (via `projenrc.js`) to mitigate the issue.\n\n### References\n\nThe `rebuild-bot.yml` workflow managed by `projen` is only one occurrence of a GitHub Workflows mis-configuration, but it may also be present in other workflows not managed by `projen` (either hand-written, or managed by other tools). For more information on this class of issues, the [Keeping your GitHub Actions and workflows secure: Preventing pwn requests][1] article provides a great overview of the problem.\n \n\n[1]: https://securitylab.github.com/research/github-actions-preventing-pwn-requests",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "projen"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.6.0"
      }, {
        "fixed" : "0.16.41"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "projen"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.16.41"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2021-21423"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/projen/projen"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/projen/PYSEC-2021-111.yaml"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/package/projen"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-527" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-04-06T18:36:19Z",
    "nvd_published_at" : "2021-04-06T19:15:00Z"
  }
}