CVE-2021-22262 Missing authorization in GitLab

Medium 5.4 Published Updated

Non-admin Jira users can modify Jira Connect Namespaces in GitLab when Jira Cloud integration is enabled.

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-22262?

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

Official description

Missing access control in all GitLab versions starting from 13.12 before 14.0.9, all versions starting from 14.1 before 14.1.4, and all versions starting from 14.2 before 14.2.2 with Jira Cloud integration enabled allows Jira users without administrative privileges to add and remove Jira Connect Namespaces via the GitLab.com for Jira Cloud application configuration page

Weakness: CWE-863

Which versions are affected by CVE-2021-22262?

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

PackageAffectedFixed in
gitlab BitnamiFrom 13.12.014.0.9, 14.1.4, 14.2.2

Products include Gitlab Gitlab.

How do I fix CVE-2021-22262?

Upgrade gitlab to a fixed version for your release line: 14.0.9, 14.1.4 or 14.2.2.

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

Is CVE-2021-22262 being exploited?

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

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2021-22262, GHSA-j34f-v6r4-25vh, UBUNTU-CVE-2021-22262.

Is CVE-2021-22262 in your software?

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

Check your SBOMs for free