Root-account takeover via plaintext migration logging
Published Nov 4, 2021 · Updated Aug 4, 2024
Sensitive-data logging in GitLab CE/EE before 14.2.6, 14.3.0 through 14.3.3, and 14.4.0 allows local users to obtain the root password. The production database seed fixture prints the configured initial root password in plaintext while migrations run, placing the credential in the migration log. Access to the local filesystem or a shipped copy of that log is required; the exposed credential grants GitLab root-account privileges.
Summary
What happened
Sensitive-data logging in GitLab CE/EE before 14.2.6, 14.3.0 through 14.3.3, and 14.4.0 allows local users to obtain the root password. The production database seed fixture prints the configured initial root password in plaintext while migrations run, placing the credential in the migration log. Access to the local filesystem or a shipped copy of that log is required; the exposed credential grants GitLab root-account privileges.
The record
- CVE
- CVE-2021-39913
- Published
- Nov 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Nov 4, 2021CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<14.2.6
- Affected versionversion=>=14.3, <14.3.4
- Affected versionversion=>=14.4, <14.4.1
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