Session compromise via marshalled Redis storage
Published Mar 26, 2021 · Updated Aug 3, 2024
Insecure session storage in affected GitLab 13.7, 13.8, and 13.9 releases allows privileged local users to read or alter Redis sessions. The session store serializes web-session contents with Ruby Marshal and writes the resulting payloads directly under session keys in Redis. Exploitation requires high-privilege local access to the Redis-backed session store; confidentiality and session integrity are exposed, but service interruption is not reported.
Summary
What happened
Insecure session storage in affected GitLab 13.7, 13.8, and 13.9 releases allows privileged local users to read or alter Redis sessions. The session store serializes web-session contents with Ruby Marshal and writes the resulting payloads directly under session keys in Redis. Exploitation requires high-privilege local access to the Redis-backed session store; confidentiality and session integrity are exposed, but service interruption is not reported.
The record
- CVE
- CVE-2021-22194
- Published
- Mar 26, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-312, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Mar 26, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.7.8
- Affected versionversion=>=13.8, <13.8.5
- Affected versionversion=>=13.9, <13.9.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
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