dbcve.org
Sonargraph IntegrationApplication · Jenkins

CVE-2023-35145

MEDIUM · 5.4 CVSS v3.1 Published 2023-06-14
Fix available
A fix is available. Upgrade to after 5.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Jenkins Sonargraph Integration Plugin 5.0.1 and earlier does not escape the file path and the project name for the Log file field form validation, resulting in a stored cross-site scripting vulnerability exploitable by attackers with Item/Configure permission.

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 Sonargraph Integration Plugin versions 5.0.1 and earlier contain a stored cross-site scripting (XSS) vulnerability in the Log file field form validation. The plugin fails to properly escape the file path and project name parameters before rendering them in the response, allowing an attacker with Item/Configure permission to inject malicious JavaScript code that executes when other users view the affected page.

MitigationUpgrade to Jenkins Sonargraph Integration Plugin version 5.0.2 or later, which properly escapes output in form validation responses. Until then, restrict Item/Configure 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
Sonargraph IntegrationApplication
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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 Sonargraph Integration plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Sonargraph Integration' in the list of installed plugins
    Affected if The plugin appears in the installed plugins list
  2. Determine the installed plugin version
    In the installed plugins list, locate the Sonargraph Integration plugin and note the Version column
    Affected if The version is 5.0.1 or earlier (any version <= 5.0.1)
  3. Check if vulnerable form validation is reachable
    Navigate to a job configured with Sonargraph Integration (Job > Configure) and locate any Log file path or Project name fields that use Sonargraph validation
    Affected if The form contains Sonargraph-related fields and the plugin version is <= 5.0.1
  4. Review Item/Configure permission assignments
    Navigate to Jenkins > Manage Jenkins > Manage Users and check which users have Item/Configure permission, or go to Job > Configure > This project is parameterized (if applicable) to see who can configure
    Affected if Any untrusted or non-admin user has Item/Configure permission and plugin version is <= 5.0.1

A user is affected if the Sonargraph Integration plugin version 5.0.1 or earlier is installed and untrusted users have Item/Configure permission on jobs using Sonargraph configuration.

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 to Jenkins Sonargraph Integration Plugin version 5.0.2 or later, which properly escapes output in form validation responses. Until then, restrict Item/Configure permission to trusted users only.

Recommended fix High confidence

Sonargraph Integration plugin version 5.0.2 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Go to the 'Installed' tab and locate the Sonargraph Integration plugin
  3. Check if version 5.0.2 or later is available in the 'Available' tab
  4. If a newer version is available, select it and click 'Download now and install after restart'
  5. After installation, verify the plugin version is 5.0.2 or later

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

Fix this in Sonargraph Integration Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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