dbcve.org
Elasticbox CiApplication · Jenkins

CVE-2023-37964

HIGH · 8.8 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 5.0.1 or later.
See remediation →
95/100
Remediation priority · Urgent
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
A cross-site request forgery (CSRF) vulnerability in Jenkins ElasticBox CI Plugin 5.0.1 and earlier allows attackers to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.

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 ElasticBox CI Plugin versions 5.0.1 and earlier contains a CSRF vulnerability that allows authenticated or unauthenticated attackers to trigger actions that connect to attacker-controlled URLs using attacker-specified Jenkins credentials IDs. This enables credential harvesting by proxying authentication requests through the Jenkins server.

MitigationUpgrade the ElasticBox CI Plugin to version 5.0.2 or later, or disable the plugin if no update is available. Restrict access to Jenkins administrative interfaces as a defense-in-depth 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
Elasticbox CiApplication
Affected:<= 5.0.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify if ElasticBox CI Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'ElasticBox' or 'Elasticbox' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Check the installed plugin version
    In the Installed plugins list, locate the ElasticBox CI Plugin and note the Version column. Compare this version to 5.0.1
    Affected if The installed version is 5.0.1 or earlier
  3. Verify if plugin is enabled
    Go to Manage Jenkins > Configure System and look for an 'ElasticBox' configuration section or similar ElasticBox-related settings
    Affected if ElasticBox configuration section exists and is not empty or disabled
  4. Check for configured credentials
    Navigate to Manage Jenkins > Credentials and examine if any ElasticBox-related credentials are stored, particularly look for credential entries associated with ElasticBox cloud connections
    Affected if Credentials are defined and bound to ElasticBox plugin configuration
  5. Review network access controls
    Inspect Jenkins logs (Manage Jenkins > System Log) for outgoing connections from Jenkins to unfamiliar URLs, or check if network policies restrict outbound connections from the Jenkins server
    Affected if Jenkins can make arbitrary outbound HTTP connections and the plugin is active

A user is affected if the ElasticBox CI Plugin is installed with version 5.0.1 or earlier and the plugin configuration or credentials are accessible via network.

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

Upgrade the ElasticBox CI Plugin to version 5.0.2 or later, or disable the plugin if no update is available. Restrict access to Jenkins administrative interfaces as a defense-in-depth measure.

Recommended fix Moderate confidence

Upgrade to the fixed version of ElasticBox CI Plugin (check Jenkins security advisory for exact version number, likely 5.0.2 or later)

  1. 1. Check the Jenkins security advisory (https://www.jenkins.io/security/advisories/) for the ElasticBox CI Plugin advisory related to CVE-2023-37964 to confirm the fixed version
  2. 2. In Jenkins, go to Manage Jenkins > Manage Plugins > Installed
  3. 3. Locate the ElasticBox CI Plugin in the list
  4. 4. If a newer version than 5.0.1 is available in the Updates tab, click 'Download now and install after restart'
  5. 5. After the plugin updates, restart Jenkins to apply the changes
  6. 6. Verify the new version is installed by checking the plugin's details
Caveat Review plugin release notes for any configuration or feature changes between versions

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

Fix this in Elasticbox Ci 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-2023-37964 — 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-2023-37964 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