dbcve.org
GitLabApplication

CVE-2022-3279

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-17
Fix available
A fix is available. Upgrade to 15.2.5 / 15.3.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
An unhandled exception in job log parsing in GitLab CE/EE affecting all versions prior to 15.2.5, 15.3 prior to 15.3.4, and 15.4 prior to 15.4.1 allows an attacker to prevent access to job logs

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 confidence

An unhandled exception in job log parsing in GitLab CE/EE allows an attacker to trigger a denial of service by causing the parsing to fail, preventing legitimate users from accessing job logs.

MitigationUpgrade GitLab to version 15.2.5, 15.3.4, 15.4.1 or later to patch the unhandled exception in job log parsing.

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
Affected:< 15.2.5>= 15.3, < 15.3.4>= 15.4, < 15.4.1

CVSS 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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check GitLab installation method and version
    Run `gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` for Omnibus installations, or `cat version` in the source directory for source installations. For Docker, check the image tag used.
    Affected if The installed version falls within < 15.2.5, >= 15.3.0 and < 15.3.4, or >= 15.4.0 and < 15.4.1
  2. Confirm GitLab edition
    Run `gitlab-rake gitlab:git:version` or check the admin area dashboard. The CVE affects both Community Edition (CE) and Enterprise Edition (EE).
    Affected if The installation is GitLab CE or EE of any vulnerable version shown in step 1
  3. Verify job log functionality is accessible
    Attempt to view a CI/CD job log by navigating to a project's pipeline > specific job > job output. The vulnerability causes an unhandled exception that prevents job logs from rendering.
    Affected if Job logs fail to load and display an error instead of the log content, indicating the parsing exception is occurring

A user is affected if their GitLab version is 15.2.x before 15.2.5, 15.3.x before 15.3.4, or 15.4.0, and job log viewing triggers an unhandled exception error.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.2.5 / 15.3.4 / 15.4.1 or later
Fixed in 15.2.515.3.415.4.1
Interim mitigation

Upgrade GitLab to version 15.2.5, 15.3.4, 15.4.1 or later to patch the unhandled exception in job log parsing.

Recommended fix High confidence

Upgrade to 15.2.5, 15.3.4, or 15.4.1 (or latest stable release in your version branch)

  1. 1. Identify current GitLab version by navigating to Admin Area > Overview > Dashboard or running `gitlab-rake gitlab:env:info`
  2. 2. Determine the appropriate upgrade path based on current version: if < 15.2.5 upgrade to 15.2.5; if >= 15.3.x and < 15.3.4 upgrade to 15.3.4; if >= 15.4.x and < 15.4.1 upgrade to 15.4.1
  3. 3. Review GitLab upgrade documentation for your installation method (Omnibus or source) at docs.gitlab.com/ee/update
  4. 4. Create a full backup before upgrading using `gitlab-backup-create` or the appropriate method for your installation
  5. 5. Stop GitLab services using `gitlab-ctl stop` (Omnibus) or stop the application server (source)
  6. 6. Update GitLab packages/repositories to the target version and run upgrade commands: for Omnibus use `apt-get update && apt-get install gitlab-ce` or `yum install gitlab-ce`; for source follow the source installation guide
  7. 7. Reconfigure GitLab using `gitlab-ctl reconfigure` (Omnibus) or rebuild the application (source)
  8. 8. Start GitLab services using `gitlab-ctl start` (Omnibus)
Caveat Minor version upgrades within the same major.minor are generally safe; review GitLab release notes for any configuration or database migration requirements

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,220
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,952.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3279 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3279 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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