Private feed disclosure via stale sessionless tokens
Published Jan 18, 2022 · Updated Aug 2, 2024
Data exposure in GitLab before 14.4.5, 14.5.0 through 14.5.2, and 14.6.0 through 14.6.1 allows remote authenticated users to read private feed data. The sessionless authentication concern accepts existing RSS and iCalendar feed tokens without rejecting users whose passwords have expired. Exploitation requires prior possession of the user's token and access to internal or private projects; the demonstrated consequence is read-only disclosure.
Summary
What happened
Data exposure in GitLab before 14.4.5, 14.5.0 through 14.5.2, and 14.6.0 through 14.6.1 allows remote authenticated users to read private feed data. The sessionless authentication concern accepts existing RSS and iCalendar feed tokens without rejecting users whose passwords have expired. Exploitation requires prior possession of the user's token and access to internal or private projects; the demonstrated consequence is read-only disclosure.
The record
- CVE
- CVE-2022-0093
- Published
- Jan 18, 2022
- Updated
- Aug 2, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- T1213.003
- Attack vector
- network
- Privileges
- authenticated
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=<14.4.5
- Affected versionversion=>=14.5.0, <14.5.3
- Affected versionversion=>=14.6.0, <14.6.1
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.
Weakness, pattern, technique
Public exploit references
- Expired-password feed-token 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