What is the severity of CVE-2022-4335?

CVE-2022-4335 is classified as a moderate severity vulnerability that could lead to unauthorized access.

How do I fix CVE-2022-4335?

To mitigate CVE-2022-4335, you should upgrade GitLab to version 15.4.6, 15.5.5, or 15.6.1 and later.

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

CVE-2022-4335 affects all versions of GitLab EE before 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.

What type of vulnerability is CVE-2022-4335?

CVE-2022-4335 is a blind Server-Side Request Forgery (SSRF) vulnerability.

Can CVE-2022-4335 allow an attacker access to internal services?

Yes, CVE-2022-4335 allows an attacker to connect to a local host, potentially accessing internal services.

Vulnerability/
CVE-2022-4335

medium

4.3

CWE

918

27/1/2023

3/8/2024

CVE-2022-4335: SSRF

First published: Fri Jan 27 2023(Updated: )

A blind SSRF vulnerability was identified in all versions of GitLab EE prior to 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1 which allows an attacker to connect to a local host.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	<15.4.6
GitLab	>=15.5.0<15.5.5
GitLab	>=15.6<15.6.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-4335?
CVE-2022-4335 is classified as a moderate severity vulnerability that could lead to unauthorized access.
How do I fix CVE-2022-4335?
To mitigate CVE-2022-4335, you should upgrade GitLab to version 15.4.6, 15.5.5, or 15.6.1 and later.
Which versions of GitLab are affected by CVE-2022-4335?
CVE-2022-4335 affects all versions of GitLab EE before 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.
What type of vulnerability is CVE-2022-4335?
CVE-2022-4335 is a blind Server-Side Request Forgery (SSRF) vulnerability.
Can CVE-2022-4335 allow an attacker access to internal services?
Yes, CVE-2022-4335 allows an attacker to connect to a local host, potentially accessing internal services.

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

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-4335?
CVE-2022-4335 is classified as a moderate severity vulnerability that could lead to unauthorized access.
How do I fix CVE-2022-4335?
To mitigate CVE-2022-4335, you should upgrade GitLab to version 15.4.6, 15.5.5, or 15.6.1 and later.
Which versions of GitLab are affected by CVE-2022-4335?
CVE-2022-4335 affects all versions of GitLab EE before 15.4.6, 15.5 prior to 15.5.5, and 15.6 prior to 15.6.1.
What type of vulnerability is CVE-2022-4335?
CVE-2022-4335 is a blind Server-Side Request Forgery (SSRF) vulnerability.
Can CVE-2022-4335 allow an attacker access to internal services?
Yes, CVE-2022-4335 allows an attacker to connect to a local host, potentially accessing internal services.