dbcve.org
Gitlab AuthenticationApplication · Jenkins

CVE-2022-27206

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-15
Fix available
A fix is available. Upgrade to after 1.13 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
Jenkins GitLab Authentication Plugin 1.13 and earlier stores the GitLab client secret unencrypted in the global config.xml file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

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

The Jenkins GitLab Authentication Plugin version 1.13 and earlier stores the GitLab OAuth client secret in plaintext within the global config.xml file on the Jenkins controller. Any user with filesystem-level access to the Jenkins controller can read this secret, compromising the OAuth credentials.

MitigationUpgrade to a patched version of the GitLab Authentication Plugin (1.14 or later) which encrypts the client secret, and rotate the exposed GitLab OAuth client credentials as a precautionary measure.

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
Gitlab AuthenticationApplication
Affected:<= 1.13

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
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 checks

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

  1. Verify GitLab Authentication Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or inspect the $JENKINS_HOME/plugins directory for a folder named gitlab-auth or similar
    Affected if The GitLab Authentication Plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the Manage Plugins UI, find the GitLab Authentication Plugin and note the version number shown, or check the plugin's manifest file (MANIFEST.MF) inside the plugin directory
    Affected if The version is 1.13 or earlier
  3. Check if OAuth is configured
    Navigate to Manage Jenkins > Configure Global Security and look for the GitLab Authentication section, or inspect $JENKINS_HOME/config.xml for a <gitlab> configuration section containing <clientSecret>
    Affected if GitLab Authentication is enabled and a <clientSecret> element exists in the configuration
  4. Verify the secret is stored in plaintext
    Open $JENKINS_HOME/config.xml in a text editor or use a command like grep to search for the <clientSecret> tag within the <gitlab> section
    Affected if The <clientSecret> value appears as readable plaintext rather than an encrypted or masked value

You are affected if the GitLab Authentication Plugin version is 1.13 or earlier and the config.xml file contains an plaintext OAuth client secret in the GitLab configuration section.

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 a release after 1.13
Interim mitigation

Upgrade to a patched version of the GitLab Authentication Plugin (1.14 or later) which encrypts the client secret, and rotate the exposed GitLab OAuth client credentials as a precautionary measure.

Recommended fix High confidence

GitLab Authentication Plugin version 1.13.1 or later

  1. Navigate to Jenkins dashboard > Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate the GitLab Authentication Plugin
  3. Check the current version - if it is 1.13 or earlier, an upgrade is required
  4. Locate the 'GitLab Authentication' plugin in the 'Available' tab or use the 'Check now' button to refresh plugin data
  5. Select the latest version of GitLab Authentication Plugin (1.13.1 or later) and click 'Install without restart' or 'Download now and install after restart'
  6. After installation, verify the new version in Manage Plugins > Installed tab
  7. Restart Jenkins if required after the plugin update
  8. After upgrade, re-configure the GitLab authentication settings to ensure credentials are stored with proper encryption
Caveat Review GitLab API token permissions after upgrade as the credential storage mechanism has changed; plugin may require Jenkins restart

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

Fix this in Gitlab Authentication Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27206 — 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-27206 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