What is the severity of CVE-2023-0485?

CVE-2023-0485 has been rated as a medium severity vulnerability.

How do I fix CVE-2023-0485?

To resolve CVE-2023-0485, upgrade your GitLab instance to version 15.8.5 or later, or to version 15.9.4 or later.

Who is affected by CVE-2023-0485?

CVE-2023-0485 affects all GitLab versions starting from 13.11 before 15.8.5, all versions from 15.9 before 15.9.4, and all versions from 15.10 before 15.10.1.

What type of vulnerability is CVE-2023-0485?

CVE-2023-0485 is a security vulnerability that allows a demoted project member to read project updates through specific actions.

Is there any workaround for CVE-2023-0485?

There are no official workarounds for CVE-2023-0485; upgrading to a fixed version is the recommended action.

Vulnerability/
CVE-2023-0485

medium

6.5

CWE

668

3/5/2023

2/8/2024

CVE-2023-0485

First published: Wed May 03 2023(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 13.11 before 15.8.5, all versions starting from 15.9 before 15.9.4, all versions starting from 15.10 before 15.10.1. It was possible that a project member demoted to a user role to read project updates by doing a diff with a pre-existing fork.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.11<15.8.5
GitLab	>=15.9<15.9.4
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-0485?
CVE-2023-0485 has been rated as a medium severity vulnerability.
How do I fix CVE-2023-0485?
To resolve CVE-2023-0485, upgrade your GitLab instance to version 15.8.5 or later, or to version 15.9.4 or later.
Who is affected by CVE-2023-0485?
CVE-2023-0485 affects all GitLab versions starting from 13.11 before 15.8.5, all versions from 15.9 before 15.9.4, and all versions from 15.10 before 15.10.1.
What type of vulnerability is CVE-2023-0485?
CVE-2023-0485 is a security vulnerability that allows a demoted project member to read project updates through specific actions.
Is there any workaround for CVE-2023-0485?
There are no official workarounds for CVE-2023-0485; upgrading to a fixed version is the recommended action.

collector/nvd-latest
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/13.11
version/gitlab/15.9
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-0485?
CVE-2023-0485 has been rated as a medium severity vulnerability.
How do I fix CVE-2023-0485?
To resolve CVE-2023-0485, upgrade your GitLab instance to version 15.8.5 or later, or to version 15.9.4 or later.
Who is affected by CVE-2023-0485?
CVE-2023-0485 affects all GitLab versions starting from 13.11 before 15.8.5, all versions from 15.9 before 15.9.4, and all versions from 15.10 before 15.10.1.
What type of vulnerability is CVE-2023-0485?
CVE-2023-0485 is a security vulnerability that allows a demoted project member to read project updates through specific actions.
Is there any workaround for CVE-2023-0485?
There are no official workarounds for CVE-2023-0485; upgrading to a fixed version is the recommended action.