Sensitive-data disclosure via unsafe License cache serialization
Published Oct 17, 2022 · Updated May 13, 2025
Sensitive-data exposure in GitLab EE 14.9 through 15.2.4, 15.3 through 15.3.3, and 15.4.0 allows remote authenticated users to read cache data. The License model enables JsonCache's unsafe_serialization_hash option, causing sensitive License attributes to be serialized into the shared cache. Low-privileged network access is required; the public record does not identify the cache retrieval path or exact fields exposed.
Summary
What happened
Sensitive-data exposure in GitLab EE 14.9 through 15.2.4, 15.3 through 15.3.3, and 15.4.0 allows remote authenticated users to read cache data. The License model enables JsonCache's unsafe_serialization_hash option, causing sensitive License attributes to be serialized into the shared cache. Low-privileged network access is required; the public record does not identify the cache retrieval path or exact fields exposed.
The record
- CVE
- CVE-2022-3291
- Published
- Oct 17, 2022
- Updated
- May 13, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- May 13, 2025Record 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.9, <15.2.5
- Affected versionversion=>=15.3, <15.3.4
- Affected versionversion=>=15.4, <15.4.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
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