CVE-2022-29220: No verification of commits origin in github-action-merge-dependabot
github-action-merge-dependabot is an action that automatically approves and merges dependabot pull requests (PRs). Prior to version 3.2.0, github-action-merge-dependabot does not check if a commit created by dependabot is verified with the proper GPG key. There is just a check if the actor is set to dependabot[bot] to determine if the PR is a legit PR. Theoretically, an owner of a seemingly valid and legit action in the pipeline can check if the PR is created by dependabot and if their own action has enough permissions to modify the PR in the pipeline. If so, they can modify the PR by adding a second seemingly valid and legit commit to the PR, as they can set arbitrarily the username and email in for commits in git. Because the bot only checks if the actor is valid, it would pass the malicious changes through and merge the PR automatically, without getting noticed by project maintainers. It would probably not be possible to determine where the malicious commit came from, as it would only say dependabot[bot] and the corresponding email-address. Version 3.2.0 contains a patch for this issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2022-29220?
CVE-2022-29220 is classified as a high-severity vulnerability due to its potential impact on repository security.
How do I fix CVE-2022-29220?
To fix CVE-2022-29220, update the github-action-merge-dependabot to version 3.2.0 or higher.
What is the main issue with CVE-2022-29220?
The main issue with CVE-2022-29220 is that it does not verify if commits created by dependabot are signed with the appropriate GPG key.
Which versions are affected by CVE-2022-29220?
CVE-2022-29220 affects all versions of github-action-merge-dependabot prior to version 3.2.0.
Is CVE-2022-29220 related to dependency management?
Yes, CVE-2022-29220 is directly related to the management of dependabot pull requests in GitHub actions.