Private project-name disclosure via GraphQL epic notes
Published Feb 5, 2020 · Updated Aug 4, 2024
Incorrect access control in GitLab EE 12.4 and later through 12.7.2 allows remote attackers to read private project names via GraphQL. The epic notes GraphQL resolver returns system-note bodies referencing issues in private projects without checking visibility of every referenced object. An unauthenticated requester needs access to a public group epic and can learn linked private-project names, but not repository contents.
Summary
What happened
Incorrect access control in GitLab EE 12.4 and later through 12.7.2 allows remote attackers to read private project names via GraphQL. The epic notes GraphQL resolver returns system-note bodies referencing issues in private projects without checking visibility of every referenced object. An unauthenticated requester needs access to a public group epic and can learn linked private-project names, but not repository contents.
The record
- CVE
- CVE-2020-7976
- Published
- Feb 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 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
No public exploit references are available in this record.
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