What is the severity of CVE-2022-1188?

CVE-2022-1188 has been classified as a medium severity vulnerability due to its potential for exploiting blind SSRF attacks.

How do I fix CVE-2022-1188?

To fix CVE-2022-1188, upgrade your GitLab instance to versions 14.7.7, 14.8.5, or 14.9.2 or later.

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

CVE-2022-1188 affects GitLab versions from 12.1.0 to below 14.7.7, 14.8.0 to below 14.8.5, and 14.9.0 to below 14.9.2.

What type of attack does CVE-2022-1188 allow?

CVE-2022-1188 allows a blind Server-Side Request Forgery (SSRF) attack through the repository mirroring feature.

Who discovered CVE-2022-1188?

CVE-2022-1188 was reported through GitLab's issue tracking and security reporting frameworks.

Vulnerability/
CVE-2022-1188

medium

5.3

CWE

918

4/4/2022

2/8/2024

CVE-2022-1188: SSRF

First published: Mon Apr 04 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting from 12.1 before 14.7.7, all versions starting from 14.8 before 14.8.5, all versions starting from 14.9 before 14.9.2 where a blind SSRF attack through the repository mirroring feature was possible.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.1.0<14.7.7
GitLab	>=12.1.0<14.7.7
GitLab	>=14.8.0<14.8.5
GitLab	>=14.8.0<14.8.5
GitLab	>=14.9.0<14.9.2
GitLab	>=14.9.0<14.9.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-1188?
CVE-2022-1188 has been classified as a medium severity vulnerability due to its potential for exploiting blind SSRF attacks.
How do I fix CVE-2022-1188?
To fix CVE-2022-1188, upgrade your GitLab instance to versions 14.7.7, 14.8.5, or 14.9.2 or later.
Which versions of GitLab are affected by CVE-2022-1188?
CVE-2022-1188 affects GitLab versions from 12.1.0 to below 14.7.7, 14.8.0 to below 14.8.5, and 14.9.0 to below 14.9.2.
What type of attack does CVE-2022-1188 allow?
CVE-2022-1188 allows a blind Server-Side Request Forgery (SSRF) attack through the repository mirroring feature.
Who discovered CVE-2022-1188?
CVE-2022-1188 was reported through GitLab's issue tracking and security reporting frameworks.

agent/type
agent/references
agent/weakness
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/12.1.0
version/gitlab/14.8.0
version/gitlab/14.9.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-1188?
CVE-2022-1188 has been classified as a medium severity vulnerability due to its potential for exploiting blind SSRF attacks.
How do I fix CVE-2022-1188?
To fix CVE-2022-1188, upgrade your GitLab instance to versions 14.7.7, 14.8.5, or 14.9.2 or later.
Which versions of GitLab are affected by CVE-2022-1188?
CVE-2022-1188 affects GitLab versions from 12.1.0 to below 14.7.7, 14.8.0 to below 14.8.5, and 14.9.0 to below 14.9.2.
What type of attack does CVE-2022-1188 allow?
CVE-2022-1188 allows a blind Server-Side Request Forgery (SSRF) attack through the repository mirroring feature.
Who discovered CVE-2022-1188?
CVE-2022-1188 was reported through GitLab's issue tracking and security reporting frameworks.