dbcve.org
Sumologic PublisherApplication · Jenkins

CVE-2023-37958

HIGH · 8.8 CVSS v3.1 Published 2023-07-12
Fix available
A fix is available. Upgrade to after 2.2.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 Sumologic Publisher Plugin 2.2.1 and earlier allows attackers 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 · moderate confidence

A CSRF vulnerability in Jenkins Sumologic Publisher Plugin versions 2.2.1 and earlier allows attackers to trick the Jenkins server into making HTTP requests to attacker-controlled URLs, potentially enabling data exfiltration or exploitation of internal services.

MitigationUpdate to a patched version of the Sumologic Publisher plugin (check Jenkins plugin repository for latest release), or disable the plugin if no patched version is available.

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
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. Verify Sumologic Publisher plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins. Look for 'Sumologic Publisher' in the plugin list.
    Affected if The Sumologic Publisher plugin appears in the installed plugins list
  2. Identify the installed version of Sumologic Publisher
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find Sumologic Publisher and note the version number displayed in the Version column. Alternatively, check the plugin's manifest file (META-INF/MANIFEST.MF) in the plugin's .hpi file located in $JENKINS_HOME/plugins/
    Affected if The installed version is 2.2.1 or earlier
  3. Confirm the plugin is enabled and active
    Check if the Sumologic Publisher plugin is not disabled: go to Manage Jenkins > Manage Plugins > Installed tab and verify the plugin status. Also check if any jobs or configurations reference Sumologic Publisher functionality.
    Affected if The plugin is installed and not explicitly disabled, meaning it can be invoked in build processes or configurations
  4. Review plugin configuration for exposed endpoints
    Examine Jenkins system configuration (Manage Jenkins > Configure System) for any Sumologic Publisher-related settings, particularly URLs or endpoints configured for data submission.
    Affected if The plugin has active configurations that could be triggered to make outbound HTTP requests

You are affected if the Sumologic Publisher plugin is installed with version 2.2.1 or earlier and the plugin is enabled or configured in 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 2.2.1
Interim mitigation

Update to a patched version of the Sumologic Publisher plugin (check Jenkins plugin repository for latest release), or disable the plugin if no patched version is available.

Recommended fix Moderate confidence

Sumologic Publisher version 2.2.2 or later

  1. Navigate to Jenkins Manage Plugins page
  2. Locate the Sumologic Publisher plugin in the Installed tab
  3. Check for updates or upgrade to version 2.2.2 or later
  4. Restart Jenkins if required to apply the update
  5. Verify the plugin upgraded successfully in the Installed plugins list

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

Fix this in Sumologic Publisher Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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