dbcve.org
Continuous Integration With Toad EdgeWeb browser · Jenkins

CVE-2022-28145

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 2.3 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 Continuous Integration with Toad Edge Plugin 2.3 and earlier does not apply Content-Security-Policy headers to report files it serves, resulting in a stored cross-site scripting (XSS) exploitable by attackers with Item/Configure permission or otherwise able to control report contents.

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

Jenkins Toad Edge Plugin versions 2.3 and earlier fails to apply Content-Security-Policy headers when serving report files, creating a stored XSS vulnerability. Attackers with Item/Configure permission or the ability to control report file contents can inject malicious scripts that execute in victims' browsers when viewing these reports.

MitigationApply CSP headers to all report files served by the plugin, or update to a patched version once available. Restrict Item/Configure permissions to minimize attack surface.

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
Continuous Integration With Toad EdgeWeb browser
Affected:<= 2.3

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. Verify Toad Edge plugin is installed
    In Jenkins, go to Manage Jenkins > Manage Plugins > Installed tab, search for 'Toad Edge' and confirm it appears in the list. Alternatively, check the $JENKINS_HOME/plugins directory for the toad-edge folder.
    Affected if The plugin is present in the installed plugins list
  2. Check installed plugin version
    In Jenkins > Manage Jenkins > Manage Plugins > Installed tab, find Toad Edge and note the version column. If not visible there, check the plugin's manifest file at $JENKINS_HOME/plugins/toad-edge/META-INF/MANIFEST.MF for the Implementation-Version.
    Affected if Version is 2.3 or earlier, or if the version cannot be determined but the plugin is present
  3. Identify if report generation is in use
    Check Jenkins job configurations for builds using Toad Edge steps, or examine $JENKINS_HOME/jobs/<jobname>/builds/ for artifacts with extensions like .html, .xml, or Toad-specific report formats generated by the plugin.
    Affected if The plugin has been used to generate reports that are stored as build artifacts
  4. Test for missing CSP headers on report files
    Trigger a job that generates Toad Edge reports, then view a report artifact in the browser. Use browser developer tools (Network tab) or curl -I <report_url> to inspect response headers. Look specifically for Content-Security-Policy header.
    Affected if The Content-Security-Policy header is absent from HTTP responses serving report files, while the same files contain user-controllable content that could host script injections

A user is affected if the Toad Edge plugin version 2.3 or earlier is installed AND report files are being generated and served without Content-Security-Policy headers.

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

Apply CSP headers to all report files served by the plugin, or update to a patched version once available. Restrict Item/Configure permissions to minimize attack surface.

Recommended fix High confidence

Toad Edge Plugin version 2.4

  1. Log in to Jenkins as an administrator
  2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. Go to the 'Installed' tab
  4. Locate 'Continuous Integration with Toad Edge' in the list
  5. If an update is available, check the plugin and click 'Download now and install after restart'
  6. Alternatively, download the .hpi file for version 2.4 from the Jenkins plugin repository and upload it via 'Advanced' > 'Upload Plugin'
  7. Restart Jenkins to complete the installation

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

Fix this in Continuous Integration With Toad Edge Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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