Unauthorized comments via unchecked discussion ID
Published Dec 13, 2021 · Updated Aug 4, 2024
Incorrect authorization in affected GitLab EE releases allows remote authenticated users to comment on vulnerabilities they cannot access. The discussion-reply request accepts a supplied in_reply_to_discussion_id without rechecking access to the associated Vulnerability Report discussion. The caller needs an account and a known discussion ID, such as one retained from earlier access; exploitation writes an unauthorized comment without exposing report contents.
Summary
What happened
Incorrect authorization in affected GitLab EE releases allows remote authenticated users to comment on vulnerabilities they cannot access. The discussion-reply request accepts a supplied in_reply_to_discussion_id without rechecking access to the associated Vulnerability Report discussion. The caller needs an account and a known discussion ID, such as one retained from earlier access; exploitation writes an unauthorized comment without exposing report contents.
The record
- CVE
- CVE-2021-39918
- Published
- Dec 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>=11.1, <14.3.6
- Affected versionversion=>=14.4, <14.4.4
- Affected versionversion=>=14.5, <14.5.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
- GitLab issue reproduction procedureproof 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