dbcve.org
Configuration As CodeApplication · Jenkins

CVE-2022-23106

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-12
Fix available
A fix is available. Upgrade to after 1.55 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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 Configuration as Code Plugin 1.55 and earlier used a non-constant time comparison function when validating an authentication token allowing attackers to use statistical methods to obtain a valid authentication token.

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

Jenkins Configuration as Code Plugin versions 1.55 and earlier used a non-constant time comparison function when validating authentication tokens. This timing side-channel allows attackers to perform statistical analysis of response times to deduce valid tokens rather than requiring full brute-force guessing.

MitigationUpgrade Jenkins Configuration as Code Plugin to version 1.55.1 or later, which implements constant-time token comparison. If immediate upgrade is not possible, consider restricting network access to the Jenkins instance as a compensating control.

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
Configuration As CodeApplication
Affected:<= 1.55

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
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify Jenkins Configuration as Code Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep configuration-as-code
    Affected if The plugin version displayed is 1.55 or earlier
  2. Confirm plugin is active and loaded
    Check that the plugin status shows 'Enabled' in Manage Jenkins > Manage Plugins > Installed, or check $JENKINS_HOME/plugins/configuration-as-code.jpi for presence
    Affected if Plugin is installed and enabled (vulnerability requires the plugin to be loaded)
  3. Verify JCasC token-based authentication is configured
    Inspect the JCasC configuration YAML file for 'token' or 'authorizationToken' fields under the 'security' or 'globalConfiguration' sections, or check $JENKINS_HOME/jenkins.yaml
    Affected if Token-based authentication is configured in JCasC (the vulnerability only affects token validation)

You are affected if Jenkins Configuration as Code Plugin version 1.55 or earlier is installed, enabled, and token-based authentication is configured in your JCasC setup.

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.55
Interim mitigation

Upgrade Jenkins Configuration as Code Plugin to version 1.55.1 or later, which implements constant-time token comparison. If immediate upgrade is not possible, consider restricting network access to the Jenkins instance as a compensating control.

Recommended fix Moderate confidence

Configuration As Code Plugin 1.55.1 or later (verify 1.55.1+ is installed)

  1. 1. Back up your Jenkins configuration and JCasC YAML files
  2. 2. Navigate to Manage Jenkins > Manage Plugins
  3. 3. Select the 'Updates' tab
  4. 4. Find 'Configuration as Code' plugin in the list
  5. 5. Select the plugin and click 'Download now and install after restart'
  6. 6. Wait for the plugin to install and Jenkins to restart
  7. 7. Verify the plugin version is updated in Manage Plugins > Installed tab
  8. 8. Test your JCasC configuration loads correctly
Caveat Review release notes for any configuration syntax changes between your version and the upgrade version; minimal risk for point releases

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

Fix this in Configuration As Code Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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