What is the severity of CVE-2022-1460?

CVE-2022-1460 is classified as a high severity vulnerability due to its potential to allow unauthorized execution of scheduled pipelines.

How do I fix CVE-2022-1460?

To fix CVE-2022-1460, upgrade your GitLab instance to version 14.8.6, 14.9.4, or 14.10.1 or later.

Which versions of GitLab are affected by CVE-2022-1460?

CVE-2022-1460 affects GitLab versions from 9.2 to 14.8.6, 14.9 from 14.9.0 to 14.9.4, and 14.10.0.

What can a malicious user do due to CVE-2022-1460?

A malicious user can exploit CVE-2022-1460 to run scheduled pipelines without proper authorization.

Is there a workaround for CVE-2022-1460?

There is no official workaround for CVE-2022-1460; the recommended action is to apply the available updates.

Vulnerability/
CVE-2022-1460

medium

6.1

CWE

863

11/5/2022

3/8/2024

CVE-2022-1460

First published: Wed May 11 2022(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 9.2 before 14.8.6, all versions starting from 14.9 before 14.9.4, all versions starting from 14.10 before 14.10.1. GitLab was not performing correct authorizations on scheduled pipelines allowing a malicious user to run a pipeline in the context of another user.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=9.2.0<14.8.6
GitLab	>=9.2.0<14.8.6
GitLab	>=14.9.0<14.9.4
GitLab	>=14.9.0<14.9.4
GitLab	=14.10.0
GitLab	=14.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1460?
CVE-2022-1460 is classified as a high severity vulnerability due to its potential to allow unauthorized execution of scheduled pipelines.
How do I fix CVE-2022-1460?
To fix CVE-2022-1460, upgrade your GitLab instance to version 14.8.6, 14.9.4, or 14.10.1 or later.
Which versions of GitLab are affected by CVE-2022-1460?
CVE-2022-1460 affects GitLab versions from 9.2 to 14.8.6, 14.9 from 14.9.0 to 14.9.4, and 14.10.0.
What can a malicious user do due to CVE-2022-1460?
A malicious user can exploit CVE-2022-1460 to run scheduled pipelines without proper authorization.
Is there a workaround for CVE-2022-1460?
There is no official workaround for CVE-2022-1460; the recommended action is to apply the available updates.

agent/author
agent/type
agent/references
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
collector/nvd-api
agent/software-canonical-lookup-request
agent/softwarecombine
agent/tags
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/9.2.0
version/gitlab/14.9.0
version/gitlab/14.10.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-2022-1460?
CVE-2022-1460 is classified as a high severity vulnerability due to its potential to allow unauthorized execution of scheduled pipelines.
How do I fix CVE-2022-1460?
To fix CVE-2022-1460, upgrade your GitLab instance to version 14.8.6, 14.9.4, or 14.10.1 or later.
Which versions of GitLab are affected by CVE-2022-1460?
CVE-2022-1460 affects GitLab versions from 9.2 to 14.8.6, 14.9 from 14.9.0 to 14.9.4, and 14.10.0.
What can a malicious user do due to CVE-2022-1460?
A malicious user can exploit CVE-2022-1460 to run scheduled pipelines without proper authorization.
Is there a workaround for CVE-2022-1460?
There is no official workaround for CVE-2022-1460; the recommended action is to apply the available updates.