dbcve.org
Elasticbox CiApplication · Jenkins

CVE-2023-37965

HIGH · 7.1 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 5.0.1 or later.
See remediation →
77/100
Remediation priority · High
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
A missing permission check in Jenkins ElasticBox CI Plugin 5.0.1 and earlier allows attackers with Overall/Read permission 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 ElasticBox CI Plugin for Jenkins lacks proper permission checks, allowing any user with basic Overall/Read access to connect to attacker-controlled URLs using credentials IDs. This enables credential theft by leveraging minimal read-level permissions to access stored credentials through the plugin's API.

MitigationUpdate to a patched version of the ElasticBox CI Plugin and review user permissions, granting Overall/Read access only to trusted users. Consider disabling the plugin if not actively used.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Verify ElasticBox CI Plugin installation
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins script console: Jenkins.instance.pluginManager.plugins.collect { it.shortName }.grep('elasticbox')
    Affected if The ElasticBox CI plugin appears in the installed plugins list
  2. Confirm plugin version
    In the Installed plugins tab, find ElasticBox CI and note the Version column, or use the script console: Jenkins.instance.pluginManager.plugins.find { it.shortName == 'elasticbox' }.version
    Affected if The version is 5.0.1 or lower
  3. Check if plugin is active/enabled
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and verify the plugin status is 'Enabled', or check Manage Jenkins > Configure System for ElasticBox configuration sections
    Affected if The plugin shows as Enabled with existing configuration
  4. Audit users with Overall/Read permission
    Navigate to Manage Jenkins > Manage Users, or go to People to see all users with access. Check Manage Jenkins > Configure Global Security to review who has Overall/Read permission
    Affected if Any untrusted or anonymous users have Overall/Read access to the Jenkins instance

The environment is affected if the ElasticBox CI Plugin is installed at version 5.0.1 or lower and untrusted users have Overall/Read access to Jenkins.

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

Update to a patched version of the ElasticBox CI Plugin and review user permissions, granting Overall/Read access only to trusted users. Consider disabling the plugin if not actively used.

Recommended fix Moderate confidence

ElasticBox CI Plugin version higher than 5.0.1 (check Jenkins Update Center for latest available version)

  1. 1. Navigate to Manage Jenkins > Manage Plugins > Installed tab
  2. 2. Locate the ElasticBox CI Plugin in the list
  3. 3. Check if the installed version is 5.0.1 or earlier (vulnerable)
  4. 4. If vulnerable, click 'Check for updates' or go to the Available tab
  5. 5. Select ElasticBox CI Plugin and click 'Download now and install after restart'
  6. 6. Wait for the plugin to update to the fixed version
  7. 7. Restart Jenkins to complete the installation
  8. 8. Verify the new version is installed (should be higher than 5.0.1)
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
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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