Unauthenticated pipeline security-data disclosure via GraphQL fields
Published Jan 18, 2022 · Updated Aug 2, 2024
Improper authorization in affected GitLab releases allows remote attackers to read pipeline security-report data through the GraphQL API. The Pipeline.securityReportFindings and Pipeline.securityReportSummary fields were introduced without permission checks and returned restricted findings or summary data. No account or user interaction is needed, but an attacker must identify a public project and pipeline containing security results.
Summary
What happened
Improper authorization in affected GitLab releases allows remote attackers to read pipeline security-report data through the GraphQL API. The Pipeline.securityReportFindings and Pipeline.securityReportSummary fields were introduced without permission checks and returned restricted findings or summary data. No account or user interaction is needed, but an attacker must identify a public project and pipeline containing security results.
The record
- CVE
- CVE-2022-0152
- Published
- Jan 18, 2022
- Updated
- Aug 2, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-862, T1213.003
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 18, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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=>=13.10, <14.4.5
- Affected versionversion=>=14.5, <14.5.3
- Affected versionversion=>=14.6, <14.6.2
What conditions does exploitation require?
What is affected?
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
- Unauthenticated GraphQL curl reproductionfunctional · 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