Repository navigation
Merge v22 patches into 22.23.4 branch #28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
6f70fb0
Initial patch
JackStrohm-asana a8d4c9b
s3 staging script
JackStrohm-asana 0c1288a
script to build locally instead of using docker containers which don'…
JackStrohm-asana 5e0424e
update github actions to build node fibers
JackStrohm-asana 2d64ee8
fix node-fibers branchname
JackStrohm-asana b9b6b32
update staging directory
JackStrohm-asana b577cda
Add fips build workflow
JackStrohm-asana ba48e86
change fiber and package build triggers
JackStrohm-asana 9977ae6
try to fix network errors on apt-get
JackStrohm-asana 2118248
working on apt-get failures
JackStrohm-asana 5122fc2
removed push trigger
JackStrohm-asana 9260bf1
another test
JackStrohm-asana cf4884d
switch FIPS Dockerfile to Ubuntu 20.04
JackStrohm-asana 3814757
revert FIPS Dockerfile to Ubuntu 22.04
JackStrohm-asana 0824123
add robust retry logic to FIPS Dockerfile apt-get
JackStrohm-asana 39bd639
consolidate all apt-get commands into single retry block
JackStrohm-asana 18a6979
add robust retry logic to regular Node Dockerfile
JackStrohm-asana 99fede0
rename build workflows for clarity
JackStrohm-asana 0f26935
added fips to the staging script to make sure we don't have cache issues
JackStrohm-asana 829e1c9
make staging do fips and update asana codez codebase
JackStrohm-asana 6dad6fe
update lockfile instructions
JackStrohm-asana ab57e94
fix staging script: validate fibers archive and fix node_setup.bzl up…
JackStrohm-asana bd560ee
Untested support for profiler
JackStrohm-asana d2b5f7f
Install node-gyp before rebuilding pprof native binding
JackStrohm-asana 17f3b44
Fix pprof native build: use --build-from-source and find .node output
JackStrohm-asana 19c9937
Merge branch 'v22.23.4' into v22.21.1-before-cherry-pick
nneha-a File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟠 High severity blocking issue identified in your code:
The untrusted
inputs.DOCKER_FILEvalue is interpolated into a shell command, allowing command injection on the GitHub Actions runner. An attacker can execute commands and potentially steal tokens, secrets, source code, or build artifacts.More details about this
inputs.DOCKER_FILEis inserted directly into a shell command. Because workflow inputs can be supplied or influenced by an untrusted workflow invocation, shell metacharacters in that value are executed by the runner rather than treated as part of the Dockerfile path.For example, an attacker could provide this input:
The step would effectively run:
The injected command runs on the same GitHub Actions runner as
docker build, so it can read accessible environment variables, workspace files, checked-out Node source, Docker credentials, and other tokens or secrets available to the job. An attacker could then use those credentials to access repositories, publish modified artifacts, or exfiltrate source code.To resolve this comment:
✨ Commit fix suggestion
View step-by-step instructions
Add an
enventry to theExecute the Dockerfilestep to transfer the workflow input into an environment variable:DOCKER_FILE: ${{ inputs.DOCKER_FILE }}Replace the direct expression in the shell command with the quoted environment variable:
docker build -t node22_fips_build -f "./$DOCKER_FILE" .If only specific Dockerfiles are valid, validate
DOCKER_FILEagainst an allowlist before running Docker, such ascase "$DOCKER_FILE" in Dockerfile|Dockerfile.*) ;; *) exit 1 ;; esac.💬 Ignore this finding
Reply with Semgrep commands to ignore this finding.
/fp <comment>for false positive/ar <comment>for acceptable risk/other <comment>for all other reasonsAlternatively, triage in Semgrep AppSec Platform to ignore the finding created by run-shell-injection.
Please reach out to Security (go/sec-inbox) if you need help with this.
You can view more details about this finding in the Semgrep AppSec Platform.