dbcve.org
DotciApplication · Jenkins

CVE-2022-41238

CRITICAL · 9.8 CVSS v3.1 Published 2022-09-21
Fix available
A fix is available. Upgrade to after 2.40.00 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A missing permission check in Jenkins DotCi Plugin 2.40.00 and earlier allows unauthenticated attackers to trigger builds of jobs corresponding to the attacker-specified repository for attacker-specified commits.

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 DotCi Plugin versions 2.40.00 and earlier lacks a permission check in its build triggering functionality, allowing unauthenticated attackers to invoke build processes for any configured job by specifying an arbitrary repository URL and commit hash. This is a critical authorization bypass that enables remote attackers to abuse the CI/CD infrastructure without any credentials.

MitigationUpgrade the DotCi Plugin to version 2.40.01 or later which includes the missing permission check. Until patched, consider disabling the plugin or restricting network access to the Jenkins instance.

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
DotciApplication
Affected:<= 2.40.00

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if DotCi plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed, or run: Jenkins.instance.pluginManager.getPlugin('dotci') via script console
    Affected if DotCi plugin is present in the plugin list
  2. Identify the installed DotCi plugin version
    View the version in the Installed Plugins tab, or run: Jenkins.instance.pluginManager.getPlugin('dotci').getVersion() via script console
    Affected if Version is 2.40.00 or earlier (the vulnerable version range)
  3. Confirm anonymous access is enabled on Jenkins
    Check Jenkins > Manage Jenkins > Configure Global Security > Authorization section. Verify if 'Anyone can do anything' or anonymous access with overall/read permissions is enabled
    Affected if Anonymous users have permissions to trigger builds or access Jenkins API
  4. Check if DotCi build trigger endpoint is network-accessible
    Test unauthenticated access to the build trigger endpoint: http://JENKINS_URL/plugin/dotci/build?repository=REPO_URL&commit=HASH or similar DotCi trigger paths. Use curl or a browser without credentials
    Affected if The endpoint responds without requiring authentication (vulnerable to unauthenticated invocation)

You are affected if the DotCi plugin version is 2.40.00 or earlier AND anonymous users can trigger builds or access the Jenkins API without authentication.

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 2.40.00
Interim mitigation

Upgrade the DotCi Plugin to version 2.40.01 or later which includes the missing permission check. Until patched, consider disabling the plugin or restricting network access to the Jenkins instance.

Recommended fix Moderate confidence

2.40.01 or later (verify exact version from Jenkins security advisory)

  1. Check Jenkins plugin repository or Jenkins security advisory for DotCi plugin to confirm the fixed version
  2. Navigate to Manage Jenkins > Manage Plugins > Installed tab
  3. Locate the DotCi plugin in the list
  4. If a version higher than 2.40.00 is available in the Updates tab, update to that version
  5. Verify the plugin version after update to confirm the fix is applied
  6. Test that the build trigger functionality works correctly with proper authorization

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

Fix this in Dotci Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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