mayadata-io / mayadata-io/kubera-docs
[Security] Workflow update-graphql-files.yml is using vulnerable action peter-evans/create-pull-request
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The workflow update-graphql-files.yml is referencing action peter-evans/create-pull-request using references 938e6aea6f8dbdaced2064e948cb806c77fe87b8. However this reference is missing the commit 9507cdc7ac7c51349ae407533e709b92b594e6d1 which may contain fix to the some vulnerability.
The vulnerability fix that is missing by actions version could be related to:
(1) CVE fix
(2) upgrade of vulnerable dependency
(3) fix to secret leak and others.
Please consider to update the reference to the action.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the update-graphql-files.yml workflow and inspect its peter-evans/create-pull-request reference, 938e6aea6f8dbdaced2064e948cb806c77fe87b8. Compare it with the reported 9507cdc7ac7c51349ae407533e709b92b594e6d1 reference, update the workflow if appropriate, and verify that the action reference is valid and the workflow remains usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100