CVE-2021-22253 Missing authorization in GitLab

Medium 4.9 Published Updated

A former user can trigger deployments to protected environments in GitLab EE after losing access, allowing unauthorized code execution or configuration changes.

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

What is CVE-2021-22253?

CVE-2021-22253 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 23 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the necessary access to trigger deployments to protected environments under specific conditions after the access has been removed

Weakness: CWE-863

Which versions are affected by CVE-2021-22253?

1 open source package ship an affected version, including gitlab. It affects 1 product.

PackageAffectedFixed in
gitlab BitnamiFrom 13.4.013.12.9, 14.0.7, 14.1.2

Products include Gitlab Gitlab.

How do I fix CVE-2021-22253?

Upgrade gitlab to a fixed version for your release line: 13.12.9, 14.0.7 or 14.1.2.

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

Is CVE-2021-22253 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2021-22253, GHSA-q297-5xx3-gw53, UBUNTU-CVE-2021-22253.

Is CVE-2021-22253 in your software?

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

Check your SBOMs for free