What is the severity of CVE-2023-1965?

CVE-2023-1965 is considered a critical vulnerability due to its impact on access tokens.

How do I fix CVE-2023-1965?

To fix CVE-2023-1965, upgrade GitLab to version 15.9.6 or later, 15.10.5 or later, or 15.11.1 or later.

Which versions of GitLab are affected by CVE-2023-1965?

CVE-2023-1965 affects all versions of GitLab EE from 14.2 before 15.9.6, from 15.10 before 15.10.5, and from 15.11 before 15.11.1.

Can CVE-2023-1965 be exploited remotely?

Yes, CVE-2023-1965 can be exploited remotely through maliciously crafted URLs.

What component of GitLab is vulnerable in CVE-2023-1965?

CVE-2023-1965 involves a lack of verification on the RelayState parameter in GitLab EE.

Vulnerability/
CVE-2023-1965

medium

6.8

CWE

352

3/5/2023

29/1/2025

CVE-2023-1965: CSRF

First published: Wed May 03 2023(Updated: )

An issue has been discovered in GitLab EE affecting all versions starting from 14.2 before 15.9.6, all versions starting from 15.10 before 15.10.5, all versions starting from 15.11 before 15.11.1. Lack of verification on RelayState parameter allowed a maliciously crafted URL to obtain access tokens granted for 3rd party Group SAML SSO logins. This feature isn't enabled by default.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=14.2<15.9.6
GitLab	>=15.10<15.10.5
GitLab	>=15.11<15.11.1

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2023-1965?
CVE-2023-1965 is considered a critical vulnerability due to its impact on access tokens.
How do I fix CVE-2023-1965?
To fix CVE-2023-1965, upgrade GitLab to version 15.9.6 or later, 15.10.5 or later, or 15.11.1 or later.
Which versions of GitLab are affected by CVE-2023-1965?
CVE-2023-1965 affects all versions of GitLab EE from 14.2 before 15.9.6, from 15.10 before 15.10.5, and from 15.11 before 15.11.1.
Can CVE-2023-1965 be exploited remotely?
Yes, CVE-2023-1965 can be exploited remotely through maliciously crafted URLs.
What component of GitLab is vulnerable in CVE-2023-1965?
CVE-2023-1965 involves a lack of verification on the RelayState parameter in GitLab EE.

collector/nvd-latest
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/14.2
version/gitlab/15.10
version/gitlab/15.11

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-2023-1965?
CVE-2023-1965 is considered a critical vulnerability due to its impact on access tokens.
How do I fix CVE-2023-1965?
To fix CVE-2023-1965, upgrade GitLab to version 15.9.6 or later, 15.10.5 or later, or 15.11.1 or later.
Which versions of GitLab are affected by CVE-2023-1965?
CVE-2023-1965 affects all versions of GitLab EE from 14.2 before 15.9.6, from 15.10 before 15.10.5, and from 15.11 before 15.11.1.
Can CVE-2023-1965 be exploited remotely?
Yes, CVE-2023-1965 can be exploited remotely through maliciously crafted URLs.
What component of GitLab is vulnerable in CVE-2023-1965?
CVE-2023-1965 involves a lack of verification on the RelayState parameter in GitLab EE.