What is the severity of CVE-2022-0136?

CVE-2022-0136 is classified as a medium severity vulnerability.

How do I fix CVE-2022-0136?

To fix CVE-2022-0136, upgrade GitLab to version 14.5.5, 14.6.5, or 14.7.2 or later.

What systems are affected by CVE-2022-0136?

CVE-2022-0136 affects GitLab versions from 10.5 to 14.5.4, 14.6 to 14.6.4, and 14.7 to 14.7.1.

What type of attack does CVE-2022-0136 involve?

CVE-2022-0136 involves a blind SSRF (Server-Side Request Forgery) attack through the Project Import feature.

When was CVE-2022-0136 discovered?

CVE-2022-0136 was discovered and publicly identified in 2022.

Vulnerability/
CVE-2022-0136

high

8.1

CWE

918

28/3/2022

2/8/2024

CVE-2022-0136: SSRF

First published: Mon Mar 28 2022(Updated: )

A vulnerability was discovered in GitLab versions 10.5 to 14.5.4, 14.6 to 14.6.4, and 14.7 to 14.7.1. GitLab was vulnerable to a blind SSRF attack through the Project Import feature.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=10.5.0<=14.5.4
GitLab	>=14.6<=14.6.4
GitLab	>=14.7.0<=14.7.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0136?
CVE-2022-0136 is classified as a medium severity vulnerability.
How do I fix CVE-2022-0136?
To fix CVE-2022-0136, upgrade GitLab to version 14.5.5, 14.6.5, or 14.7.2 or later.
What systems are affected by CVE-2022-0136?
CVE-2022-0136 affects GitLab versions from 10.5 to 14.5.4, 14.6 to 14.6.4, and 14.7 to 14.7.1.
What type of attack does CVE-2022-0136 involve?
CVE-2022-0136 involves a blind SSRF (Server-Side Request Forgery) attack through the Project Import feature.
When was CVE-2022-0136 discovered?
CVE-2022-0136 was discovered and publicly identified in 2022.

agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/10.5.0
version/gitlab/14.5.4
version/gitlab/14.6
version/gitlab/14.6.4
version/gitlab/14.7.0
version/gitlab/14.7.1

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-0136?
CVE-2022-0136 is classified as a medium severity vulnerability.
How do I fix CVE-2022-0136?
To fix CVE-2022-0136, upgrade GitLab to version 14.5.5, 14.6.5, or 14.7.2 or later.
What systems are affected by CVE-2022-0136?
CVE-2022-0136 affects GitLab versions from 10.5 to 14.5.4, 14.6 to 14.6.4, and 14.7 to 14.7.1.
What type of attack does CVE-2022-0136 involve?
CVE-2022-0136 involves a blind SSRF (Server-Side Request Forgery) attack through the Project Import feature.
When was CVE-2022-0136 discovered?
CVE-2022-0136 was discovered and publicly identified in 2022.