Private issue metadata disclosure via stale move references
Published Apr 8, 2020 · Updated Aug 4, 2024
Information disclosure in GitLab CE and EE 8.11 through 12.9 allows remote attackers to read private-project issue metadata. Moved-issue system notes and GraphQL discussion output retain and render destination references without enforcing the destination project's visibility. A publicly visible source issue must be moved into a private project; exposed data includes the private namespace, issue title, and issue number.
Summary
What happened
Information disclosure in GitLab CE and EE 8.11 through 12.9 allows remote attackers to read private-project issue metadata. Moved-issue system notes and GraphQL discussion output retain and render destination references without enforcing the destination project's visibility. A publicly visible source issue must be moved into a private project; exposed data includes the private namespace, issue title, and issue number.
The record
- CVE
- CVE-2020-10978
- Published
- Apr 8, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 8, 2020CVE 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
Weakness, pattern, technique
Public exploit references
- GitLab moved-issue 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