dbcve.org
Continuous Integration With Toad EdgeWeb browser · Jenkins

CVE-2022-28146

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 2.3 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
Jenkins Continuous Integration with Toad Edge Plugin 2.3 and earlier allows attackers with Item/Configure permission to read arbitrary files on the Jenkins controller by specifying an input folder on the Jenkins controller as a parameter to its build steps.

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 does not properly validate input folder parameters in build steps, allowing authenticated users with Item/Configure permission to read arbitrary files from the Jenkins controller file system by specifying file paths as parameters to build steps.

MitigationUpgrade Toad Edge Plugin to version 2.4 or later. Until patched, limit Item/Configure permission to only trusted users and monitor for suspicious configuration changes.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 and search for 'Toad Edge' or 'Jenkins Continuous Integration With Toad Edge' to confirm the plugin is present.
    Affected if The plugin is not listed in installed plugins, meaning the vulnerability does not apply.
  2. Check installed Toad Edge Plugin version
    In the installed plugins list, note the version number shown for the Toad Edge Plugin. Compare this version to the affected range: 2.3 and earlier.
    Affected if The installed version is 2.3 or any version lower than 2.3, indicating the plugin is vulnerable.
  3. Verify Item/Configure permission assignments
    Go to Manage Jenkins > Manage Users and review which users or groups have Item/Configure permission. In each job's configuration, check who has permission to configure the job.
    Affected if Untrusted or unauthorized users have Item/Configure permission, creating the condition required for exploitation.
  4. Review Toad Edge build step configurations
    Examine configured jobs that use Toad Edge build steps. Look at the build step parameters, specifically any folder or path input fields that accept user-provided folder names.
    Affected if Build steps contain folder path parameters that could be manipulated to read arbitrary files.

A user is affected if they have Toad Edge Plugin version 2.3 or earlier installed AND have users with Item/Configure permission that could exploit the path validation flaw in build step parameters.

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

Upgrade Toad Edge Plugin to version 2.4 or later. Until patched, limit Item/Configure permission to only trusted users and monitor for suspicious configuration changes.

Recommended fix Moderate confidence

Version 2.4 or later

  1. 1. Navigate to Manage Jenkins > Manage Plugins
  2. 2. Go to the Installed tab
  3. 3. Locate the 'Continuous Integration With Toad Edge' plugin
  4. 4. If an update is available, update to the latest version which contains the fix for CVE-2022-28146
  5. 5. Alternatively, download the latest version from the Jenkins plugin repository and manually upload it
  6. 6. After updating, restart Jenkins to apply changes
  7. 7. Verify the plugin version shows 2.4 or later in the installed plugins list

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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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