GitLabApplication
CVE-2022-1120
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing filtering in an error message in GitLab CE/EE affecting all versions prior to 14.7.7, 14.8 prior to 14.8.5, and 14.9 prior to 14.9.2 exposed sensitive information when an include directive fails in the CI/CD configuration.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGitLab CE/EE versions prior to 14.7.7, 14.8.5, and 14.9.2 contain a missing input filtering vulnerability in CI/CD error messages. When an include directive fails in the CI/CD configuration, the error message was not properly sanitized, potentially exposing sensitive information such as credentials, tokens, or internal paths that may be present in the pipeline configuration.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
GitLabApplication
< 14.7.7>= 14.8.0, < 14.8.5>= 14.9.0, < 14.9.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check GitLab versionNavigate to Admin Area > Settings > General, or run `gitlab-rake gitlab:env:info` to display version informationAffected if Version is below 14.7.7, between 14.8.0-14.8.4, or between 14.9.0-14.9.1
-
Identify CI/CD configurationInspect project CI/CD configurations for include directives: check .gitlab-ci.yml files and project CI/CD settings for 'include:' sectionsAffected if CI/CD pipelines use include directives to reference external YAML files
-
Verify sensitive data in CI/CD configsReview CI/CD configuration files and variables for hardcoded credentials, tokens, API keys, or internal file paths in include statements or pipeline definitionsAffected if Sensitive credentials or tokens are present in CI/CD configuration files that could be exposed through error messages when include directives fail
A defender is affected if their GitLab version falls within the affected ranges (below 14.7.7, 14.8.0-14.8.4, or 14.9.0-14.9.1) AND they use CI/CD include directives with sensitive data in their pipeline configurations.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped14.7.714.8.514.9.2
Upgrade GitLab to version 14.7.7, 14.8.5, 14.9.2 or later to receive the patch. As a temporary workaround, ensure no sensitive data is present in CI/CD configuration files that could be exposed through error messages.
14.9.2 or later (14.7.7, 14.8.5, or 14.9.2 are the minimum fixed releases depending on your starting version)
- Upgrade GitLab to version 14.7.7, 14.8.5, or 14.9.2 or later
- If using GitLab SaaS, the fix is automatically applied
- After upgrade, verify CI/CD pipeline configurations do not expose sensitive variables in error messages
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in GitLab
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1120 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-1120 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data