{"api_version":"1","generated_at":"2026-07-23T14:41:52+00:00","cve":"CVE-2021-21423","urls":{"html":"https://cve.report/CVE-2021-21423","api":"https://cve.report/api/cve/CVE-2021-21423.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2021-21423","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2021-21423"},"summary":{"title":"CVE-2021-21423","description":"`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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2021-04-06 19:15:00","updated_at":"2021-04-15 14:37:00"},"problem_types":["CWE-527"],"metrics":[],"references":[{"url":"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643","name":"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643","refsource":"MISC","tags":[],"title":"fix(node): security vulnerability in rebuild-bot (#602) · projen/projen@36030c6 · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq","name":"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq","refsource":"CONFIRM","tags":[],"title":"Rebuild-bot workflow may allow unauthorised repository modifications · Advisory · projen/projen · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.npmjs.com/package/projen","name":"https://www.npmjs.com/package/projen","refsource":"MISC","tags":[],"title":"projen  -  npm","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2021-21423","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-21423","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2021","cve_id":"21423","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"projen_project","cpe5":"projen","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"node.js","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[{"cve":"CVE-2021-21423","qid":"982750","title":"Nodejs (npm) Security Update for projen (GHSA-gg2g-m5wc-vccq)"}]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2021-21423","STATE":"PUBLIC","TITLE":"Exposure of Version-Control Repository to an Unauthorized Control Sphere in projen"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"projen","version":{"version_data":[{"version_value":">= 0.6.0, < 0.16.41"}]}}]},"vendor_name":"projen"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"`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."}]},"generator":{"engine":"Vulnogram 0.0.9"},"impact":{"cvss":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.8,"baseSeverity":"MEDIUM","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-527: Exposure of Version-Control Repository to an Unauthorized Control Sphere"}]}]},"references":{"reference_data":[{"name":"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq","refsource":"CONFIRM","url":"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq"},{"name":"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643","refsource":"MISC","url":"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643"},{"name":"https://www.npmjs.com/package/projen","refsource":"MISC","url":"https://www.npmjs.com/package/projen"}]},"source":{"advisory":"GHSA-gg2g-m5wc-vccq","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2021-04-06 19:15:00","lastModifiedDate":"2021-04-15 14:37:00","problem_types":["CWE-527"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":8.1,"baseSeverity":"HIGH"},"exploitabilityScore":2.8,"impactScore":5.2},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:S/C:P/I:P/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"SINGLE","confidentialityImpact":"PARTIAL","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":5.5},"severity":"MEDIUM","exploitabilityScore":8,"impactScore":4.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:projen_project:projen:*:*:*:*:*:node.js:*:*","versionStartIncluding":"0.6.0","versionEndExcluding":"0.16.41","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2021","CveId":"21423","Ordinal":"195549","Title":"CVE-2021-21423","CVE":"CVE-2021-21423","Year":"2021"},"notes":[{"CveYear":"2021","CveId":"21423","Ordinal":"1","NoteData":"`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.","Type":"Description","Title":null},{"CveYear":"2021","CveId":"21423","Ordinal":"2","NoteData":"2021-04-06","Type":"Other","Title":"Published"},{"CveYear":"2021","CveId":"21423","Ordinal":"3","NoteData":"2021-04-06","Type":"Other","Title":"Modified"}]}}}