What is the severity of CVE-2022-0249?

The severity of CVE-2022-0249 is considered medium as it allows for a blind SSRF attack.

How do I fix CVE-2022-0249?

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

What versions of GitLab are affected by CVE-2022-0249?

CVE-2022-0249 affects GitLab versions from 12.0 up to 14.7.1, excluding 14.5.5, 14.6.5, and 14.7.2.

What type of attack is associated with CVE-2022-0249?

CVE-2022-0249 is associated with a blind SSRF (Server-Side Request Forgery) attack.

Is there a workaround for CVE-2022-0249 if I cannot upgrade GitLab?

No specific workaround is recommended for CVE-2022-0249, and upgrading is the best course of action.

Vulnerability/
CVE-2022-0249

critical

9.1

CWE

918

28/3/2022

2/8/2024

CVE-2022-0249: SSRF

First published: Mon Mar 28 2022(Updated: )

A vulnerability was discovered in GitLab starting with version 12. GitLab was vulnerable to a blind SSRF attack since requests to shared address space were not blocked.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.0<=14.5.4
GitLab	>=14.6<=14.6.4
GitLab	>=14.7<=14.7.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0249?
The severity of CVE-2022-0249 is considered medium as it allows for a blind SSRF attack.
How do I fix CVE-2022-0249?
To fix CVE-2022-0249, upgrade GitLab to version 14.5.5 or later, 14.6.5 or later, or 14.7.2 or later.
What versions of GitLab are affected by CVE-2022-0249?
CVE-2022-0249 affects GitLab versions from 12.0 up to 14.7.1, excluding 14.5.5, 14.6.5, and 14.7.2.
What type of attack is associated with CVE-2022-0249?
CVE-2022-0249 is associated with a blind SSRF (Server-Side Request Forgery) attack.
Is there a workaround for CVE-2022-0249 if I cannot upgrade GitLab?
No specific workaround is recommended for CVE-2022-0249, and upgrading is the best course of action.

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/12.0
version/gitlab/14.5.4
version/gitlab/14.6
version/gitlab/14.6.4
version/gitlab/14.7
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-0249?
The severity of CVE-2022-0249 is considered medium as it allows for a blind SSRF attack.
How do I fix CVE-2022-0249?
To fix CVE-2022-0249, upgrade GitLab to version 14.5.5 or later, 14.6.5 or later, or 14.7.2 or later.
What versions of GitLab are affected by CVE-2022-0249?
CVE-2022-0249 affects GitLab versions from 12.0 up to 14.7.1, excluding 14.5.5, 14.6.5, and 14.7.2.
What type of attack is associated with CVE-2022-0249?
CVE-2022-0249 is associated with a blind SSRF (Server-Side Request Forgery) attack.
Is there a workaround for CVE-2022-0249 if I cannot upgrade GitLab?
No specific workaround is recommended for CVE-2022-0249, and upgrading is the best course of action.