What is the severity of CVE-2021-22262?

CVE-2021-22262 is rated as a medium severity vulnerability.

How do I fix CVE-2021-22262?

To fix CVE-2021-22262, upgrade GitLab to version 14.0.9 or later, 14.1.4 or later, or 14.2.2 or later.

Which GitLab versions are affected by CVE-2021-22262?

CVE-2021-22262 affects all GitLab versions starting from 13.12 before 14.0.9, from 14.1 before 14.1.4, and from 14.2 before 14.2.2.

What kind of access issue does CVE-2021-22262 expose?

CVE-2021-22262 allows Jira users without administrative privileges to improperly add and remove Jira Connect names.

Is there a workaround for CVE-2021-22262?

Currently, there is no documented workaround for CVE-2021-22262, and upgrading is the recommended solution.

Vulnerability/
CVE-2021-22262

medium

5.4

CWE

863

5/10/2021

3/8/2024

CVE-2021-22262

First published: Tue Oct 05 2021(Updated: )

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

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.12.0<14.0.9
GitLab	>=13.12.0<14.0.9
GitLab	>=14.1.0<14.1.4
GitLab	>=14.1.0<14.1.4
GitLab	>=14.2.0<14.2.2
GitLab	>=14.2.0<14.2.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22262?
CVE-2021-22262 is rated as a medium severity vulnerability.
How do I fix CVE-2021-22262?
To fix CVE-2021-22262, upgrade GitLab to version 14.0.9 or later, 14.1.4 or later, or 14.2.2 or later.
Which GitLab versions are affected by CVE-2021-22262?
CVE-2021-22262 affects all GitLab versions starting from 13.12 before 14.0.9, from 14.1 before 14.1.4, and from 14.2 before 14.2.2.
What kind of access issue does CVE-2021-22262 expose?
CVE-2021-22262 allows Jira users without administrative privileges to improperly add and remove Jira Connect names.
Is there a workaround for CVE-2021-22262?
Currently, there is no documented workaround for CVE-2021-22262, and upgrading is the recommended solution.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.12.0
version/gitlab/14.1.0
version/gitlab/14.2.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2021-22262?
CVE-2021-22262 is rated as a medium severity vulnerability.
How do I fix CVE-2021-22262?
To fix CVE-2021-22262, upgrade GitLab to version 14.0.9 or later, 14.1.4 or later, or 14.2.2 or later.
Which GitLab versions are affected by CVE-2021-22262?
CVE-2021-22262 affects all GitLab versions starting from 13.12 before 14.0.9, from 14.1 before 14.1.4, and from 14.2 before 14.2.2.
What kind of access issue does CVE-2021-22262 expose?
CVE-2021-22262 allows Jira users without administrative privileges to improperly add and remove Jira Connect names.
Is there a workaround for CVE-2021-22262?
Currently, there is no documented workaround for CVE-2021-22262, and upgrading is the recommended solution.