Unauthenticated internal-note disclosure via new-issue route
Published Dec 16, 2024 · Updated Dec 16, 2024
Incorrect authorization in affected GitLab CE/EE releases allows remote attackers to read internal-note threads in public merge requests. The new-issue route accepts merge_request_to_resolve_discussions_of and renders unresolved internal discussions without enforcing project membership. A public project and known merge-request identifier are sufficient; no account is required, and exposure is limited to confidential note content.
Summary
What happened
Incorrect authorization in affected GitLab CE/EE releases allows remote attackers to read internal-note threads in public merge requests. The new-issue route accepts merge_request_to_resolve_discussions_of and renders unresolved internal discussions without enforcing project membership. A public project and known merge-request identifier are sufficient; no account is required, and exposure is limited to confidential note content.
The record
- CVE
- CVE-2024-8650
- Published
- Dec 16, 2024
- Updated
- Dec 16, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1213.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 16, 2024CVE publishedPublication date reported by the CVE source.
- Dec 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=15.0 <17.4.6
- Affected versionversion=17.5 <17.5.4
- Affected versionversion=17.6 <17.6.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Public merge-request internal-note disclosure reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo