dbcve.org
Batch TaskApplication · Jenkins

CVE-2022-23115

MEDIUM · 5.4 CVSS v3.1 Published 2022-01-12
Fix available
A fix is available. Upgrade to after 1.19 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cross-site request forgery (CSRF) vulnerabilities in Jenkins batch task Plugin 1.19 and earlier allows attackers with Overall/Read access to retrieve logs, build or delete a batch task.

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

This is a CSRF vulnerability in the Jenkins batch task Plugin versions 1.19 and earlier. Attackers with only Overall/Read access (typically low-privilege users) can trick authenticated users into performing unintended actions—retrieving logs, triggering builds, or deleting batch tasks—via forged HTTP requests.

MitigationUpgrade the Jenkins batch task Plugin to version 1.20 or later, which includes anti-CSRF tokens or protection mechanisms. As a compensating control, ensure users have the minimum necessary permissions and consider disabling batch task functionality if not required.

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
Batch TaskApplication
Affected:<= 1.19

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 if Batch Task Plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab and search for 'Batch Task' in the list, or check the $JENKINS_HOME/plugins directory for the batch-task plugin folder.
    Affected if The plugin is not found in the installed plugins list.
  2. Determine the installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, locate the Batch Task plugin and read the Version column. Alternatively, inspect the file $JENKINS_HOME/plugins/batch-task/META-INF/MANIFEST.MF for the Implementation-Version attribute.
    Affected if The version listed is 1.19 or earlier.
  3. Verify the CSRF protection status
    In Jenkins, go to Manage Jenkins > Configure Global Security and check if 'Prevent Cross Site Request Forgery exploits' is enabled under the CSRF Protection section. Also inspect the plugin's source code or release notes for version 1.20 to confirm whether anti-CSRF tokens were added.
    Affected if CSRF protection is disabled globally, or the plugin version is 1.19 or earlier and lacks the anti-CSRF token mechanism.
  4. Review user permissions for Batch Task access
    In Jenkins, go to Manage Jenkins > Manage and Assign Roles to see which users or groups have Overall/Read access. Check if low-privilege users can access the Batch Task functionality via /batch-tasks/ endpoints.
    Affected if Users with only Overall/Read permission have access to batch task operations.

A user is affected if the Batch Task Plugin version is 1.19 or earlier, CSRF protection is not enforced, and attackers with Overall/Read access can trick authenticated users into clicking malicious links.

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

Upgrade the Jenkins batch task Plugin to version 1.20 or later, which includes anti-CSRF tokens or protection mechanisms. As a compensating control, ensure users have the minimum necessary permissions and consider disabling batch task functionality if not required.

Recommended fix High confidence

Batch Task plugin version 1.20 or later

  1. Navigate to Jenkins Manage Plugins page
  2. Locate the 'Batch Task' plugin in the 'Installed' tab
  3. Check the current version of the Batch Task plugin - if it is 1.19 or earlier, an upgrade is needed
  4. Upgrade the Batch Task plugin to version 1.20 or later
  5. Restart Jenkins if required for the plugin update to take effect
  6. Verify the upgrade was successful by confirming the new version in the plugin manager

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

Fix this in Batch Task Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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