CVE-2024-10240: Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitLab

Q: What is the severity of CVE-2024-10240?

CVE-2024-10240 is categorized with a medium severity level due to information disclosure risks.

Q: How do I fix CVE-2024-10240?

To fix CVE-2024-10240, upgrade GitLab to version 17.3.7, 17.4.4, or 17.5.2 or later.

Q: Who is affected by CVE-2024-10240?

CVE-2024-10240 affects all GitLab EE versions from 17.3 before 17.3.7, 17.4 before 17.4.4, and 17.5 before 17.5.2.

Q: What is the nature of the vulnerability described in CVE-2024-10240?

CVE-2024-10240 allows unauthenticated users to read some information about merge requests in private repositories.

Q: When was CVE-2024-10240 disclosed?

CVE-2024-10240 was disclosed in November 2024 and has potential impacts on user data security.

Published Nov 13, 2024

Updated

An issue has been discovered in GitLab EE affecting all versions starting from 17.3 before 17.3.7, all versions starting from 17.4 before 17.4.4, all versions starting from 17.5 before 17.5.2 in which an unauthenticated user may be able to read some information about an MR in a private project, under certain circumstances.

Affected Software

7 affected componentsFixes available

GitLab GitLab>=17.3.0<17.3.7

GitLab GitLab>=17.4.0<17.4.4

GitLab GitLab>=17.5.0<17.5.2

GitLab GitLab EE>=17.3<17.3.7, >=17.4<17.4.4, >=17.5<17.5.2

17.3.717.4.417.5.2

Remediation

Information

Upgrade to version 17.5.2, 17.4.4, 17.3.7 or above

Event History

Nov 26, 2024

CVE Published

via MITRE·07:22 PM

Data Sourced

via MITRE·07:22 PM

RemedyDescriptionSeverityWeakness

Apr 22, 2026

Data Sourced

via GitLab·08:55 AM

DescriptionSeverityAffected Software

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

What is the severity of CVE-2024-10240?