dbcve.org
Sumologic PublisherApplication · Jenkins

CVE-2023-37959

MEDIUM · 6.5 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 2.2.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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 Sumologic Publisher Plugin 2.2.1 and earlier allows attackers with Overall/Read permission to connect to an attacker-specified URL.

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 Sumologic Publisher Plugin for Jenkins versions 2.2.1 and earlier lacks a permission check before allowing URL connections. Attackers with only Overall/Read permission (the lowest privilege level in Jenkins) can cause the Jenkins server to connect to attacker-specified URLs, enabling potential SSRF attacks or data exfiltration.

MitigationUpgrade to a patched version of the Sumologic Publisher Plugin that includes proper permission checks. Until an upgrade is available, restrict Overall/Read permission to trusted users only.

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
Sumologic PublisherApplication
Affected:<= 2.2.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
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 Sumologic Publisher Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or run: jenkins-cli.jar who-am-i (or check $JENKINS_HOME/plugins for sumologic-plugin directory)
    Affected if Plugin is present in the installed plugins list
  2. Determine installed plugin version
    In Jenkins UI: Go to Manage Jenkins > Manage Plugins > Installed, find 'Sumologic Publisher', note the Version column. Alternatively, check the version file in $JENKINS_HOME/plugins/sumologic-publisher/META-INF/MANIFEST.MF
    Affected if Version is 2.2.1 or lower
  3. Check if plugin is enabled
    In Jenkins UI: Manage Jenkins > Configure Global Security > Agents, ensure the plugin is not disabled. Or check $JENKINS_HOME/org.jenkinsci.plugins.SumoLogicPublisher.xml for disabled configuration
    Affected if Plugin is enabled/active in Jenkins configuration
  4. Identify jobs using Sumologic Publisher
    Search job configurations: use Jenkins CLI 'jenkins-cli.jar list-jobs' and inspect config.xml for each, or search $JENKINS_HOME/jobs/*/config.xml for '<sumologic>' or 'SumoPublisher' entries
    Affected if Any job configuration contains Sumologic Publisher build steps or publishers

Environment is affected if Sumologic Publisher Plugin version 2.2.1 or lower is installed, enabled, and configured in any job, since any user with Overall/Read permission could trigger the URL connection vulnerability.

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

Upgrade to a patched version of the Sumologic Publisher Plugin that includes proper permission checks. Until an upgrade is available, restrict Overall/Read permission to trusted users only.

Recommended fix High confidence

Upgrade to Sumologic Publisher plugin version higher than 2.2.1 (check Jenkins plugin repository for latest available secure version)

  1. 1. Navigate to the Jenkins dashboard
  2. 2. Go to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Select the 'Installed' tab
  4. 4. Locate 'Sumologic Publisher' plugin in the list
  5. 5. If an update is available, click 'Update now' to install a version newer than 2.2.1
  6. 6. Restart Jenkins if required to complete the installation
  7. 7. Verify the plugin is updated by checking the version in 'Manage Plugins' > 'Installed'

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

Fix this in Sumologic Publisher Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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