dbcve.org
Tests SelectorApplication · Jenkins

CVE-2022-28160

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 1.3.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 Tests Selector Plugin 1.3.3 and earlier allows users with Item/Configure permission to read arbitrary files on the Jenkins controller.

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 Tests Selector Plugin versions 1.3.3 and earlier contains an arbitrary file read vulnerability. Users with Item/Configure permission (a standard project-level permission) can read any file on the Jenkins controller file system by exploiting insufficient path validation in the plugin.

MitigationUpgrade Jenkins Tests Selector Plugin to version 1.4.0 or later to remediate this vulnerability.

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
Tests SelectorApplication
Affected:<= 1.3.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 Tests Selector Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, or check the JENKINS_HOME/plugins directory for tests-selector-plugin folder. Alternatively, access /pluginManager/installed via the Jenkins CLI/API.
    Affected if The Tests Selector Plugin is present in the Jenkins environment
  2. Determine installed plugin version
    In the Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed, locate Tests Selector Plugin, and note the version number displayed. Or examine the manifest file at JENKINS_HOME/plugins/tests-selector-plugin/META-INF/MANIFEST.MF
    Affected if The version is 1.3.3 or earlier
  3. Check if Job/Item Configure permission exists for users
    Navigate to Manage Jenkins > Manage Users and review user permissions. For each job, go to Configure > Authentication or check the authorization matrix. The vulnerability requires users to have Item/Configure permission.
    Affected if Non-admin users have Item/Configure permission on any project
  4. Identify accessible file system paths from job configuration
    In any job using Tests Selector, examine the job configuration page for paths configured in the Tests Selector settings. The plugin allows configuring test selection paths that could be manipulated to read arbitrary files.
    Affected if Tests Selector is configured with any file paths in job configurations

A user is affected if the Tests Selector Plugin version is 1.3.3 or earlier AND non-administrative users have Item/Configure permission on at least one project.

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 1.3.3
Interim mitigation

Upgrade Jenkins Tests Selector Plugin to version 1.4.0 or later to remediate this vulnerability.

Recommended fix High confidence

Tests Selector Plugin version 1.3.4 or later

  1. Navigate to Manage Jenkins > Manage Plugins
  2. Select the 'Installed' tab
  3. Find 'Tests Selector' plugin in the list
  4. If installed, click 'Update' to get the latest version
  5. Alternatively, download the latest .hpi from Jenkins plugin repository and upload via 'Advanced' > 'Upload Plugin'
  6. Restart Jenkins if required after plugin update

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

Fix this in Tests Selector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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