{"url":"http://public2.vulnerablecode.io/api/packages/20627?format=json","purl":"pkg:pypi/projen@0.16.39","type":"pypi","namespace":"","name":"projen","version":"0.16.39","qualifiers":{},"subpath":"","is_vulnerable":true,"next_non_vulnerable_version":"0.16.41","latest_non_vulnerable_version":"0.16.41","affected_by_vulnerabilities":[{"url":"http://public2.vulnerablecode.io/api/vulnerabilities/35769?format=json","vulnerability_id":"VCID-f26d-mud2-zfcr","summary":"`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.","references":[{"reference_url":"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643","reference_id":"","reference_type":"","scores":[],"url":"https://github.com/projen/projen/commit/36030c6a4b1acd0054673322612e7c70e9446643"},{"reference_url":"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq","reference_id":"","reference_type":"","scores":[],"url":"https://github.com/projen/projen/security/advisories/GHSA-gg2g-m5wc-vccq"},{"reference_url":"https://www.npmjs.com/package/projen","reference_id":"","reference_type":"","scores":[],"url":"https://www.npmjs.com/package/projen"}],"fixed_packages":[{"url":"http://public2.vulnerablecode.io/api/packages/20629?format=json","purl":"pkg:pypi/projen@0.16.41","is_vulnerable":false,"affected_by_vulnerabilities":[],"resource_url":"http://public2.vulnerablecode.io/packages/pkg:pypi/projen@0.16.41"}],"aliases":["CVE-2021-21423","GHSA-gg2g-m5wc-vccq","PYSEC-2021-111"],"risk_score":null,"exploitability":null,"weighted_severity":null,"resource_url":"http://public2.vulnerablecode.io/vulnerabilities/VCID-f26d-mud2-zfcr"}],"fixing_vulnerabilities":[],"risk_score":null,"resource_url":"http://public2.vulnerablecode.io/packages/pkg:pypi/projen@0.16.39"}