CVE-2022-29220 No verification of commits origin in github-action-merge-dependabot

Medium 6.5 Published Updated

Attackers can inject malicious commits into Dependabot PRs because the action fails to verify GPG signatures, allowing unauthorized code execution.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2022-29220?

CVE-2022-29220 is a medium-severity missing authorization vulnerability in fastify github-action-merge-dependabot, published on 31 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-345, CWE-283

Which versions are affected by CVE-2022-29220?

It affects 1 product.

Products include Fastify Github Action Merge Dependabot.

How do I fix CVE-2022-29220?

No fix has been published for CVE-2022-29220 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2022-29220 being exploited?

There is no known exploitation of CVE-2022-29220 in the wild and no public exploit code.

Sources

Also known as GHSA-v5vr-h3xq-8v6w.

Is CVE-2022-29220 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free