dbcve.org
Tests SelectorApplication · Jenkins

CVE-2022-28159

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-29
Fix available
A fix is available. Upgrade to after 1.3.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 Tests Selector Plugin 1.3.3 and earlier does not escape the Properties File Path option for Choosing Tests parameters, resulting in a stored cross-site scripting (XSS) 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

Jenkins Tests Selector Plugin 1.3.3 and earlier fails to escape the Properties File Path parameter when rendering it in the UI, allowing stored XSS. Attackers with Item/Configure permission can inject malicious scripts that execute when other users view the configuration.

MitigationUpgrade to a patched version of the Tests Selector Plugin. Until patched, restrict Item/Configure permissions to trusted administrators only and consider implementing Content Security Policy headers.

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
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 Tests Selector Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Tests Selector', or use the Jenkins CLI: java -jar jenkins-cli.jar list-plugins | grep -i 'tests-selector'
    Affected if The Tests Selector plugin appears in the installed plugins list
  2. Check installed plugin version
    In Manage Jenkins > Manage Plugins > Installed, find Tests Selector and note the Version column, or check the plugin's MANIFEST.mf file in the plugin's war/jar file
    Affected if Version is 1.3.3 or earlier
  3. Identify configured Jobs using Tests Selector
    Search Jenkins jobs for builds that use the Tests Selector plugin in their configuration. This can be done by reviewing job configuration pages or searching config.xml files for 'tests-selector' or 'TestsSelector' references
    Affected if Any job has the Tests Selector plugin configured with a Properties File Path parameter
  4. Check for Properties File Path configuration
    In any job using Tests Selector, go to Configure > Build Environment or relevant section and inspect the 'Properties File Path' field for any suspicious content
    Affected if The Properties File Path field contains unsanitized user input or appears to have been modified with unusual values

User is affected if Tests Selector plugin version 1.3.3 or earlier is installed AND any job has the plugin configured with a Properties File Path parameter accessible to users with Item/Configure permission.

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 to a patched version of the Tests Selector Plugin. Until patched, restrict Item/Configure permissions to trusted administrators only and consider implementing Content Security Policy headers.

Recommended fix Moderate confidence

Tests Selector plugin version 1.3.4 or later

  1. Navigate to Jenkins dashboard
  2. Go to Manage Jenkins > Manage Plugins
  3. Select the 'Installed' tab
  4. Locate the Tests Selector plugin in the list
  5. If an update is available, select the plugin and click 'Update'
  6. Restart Jenkins if required after the update
  7. Verify the plugin has been updated to version 1.3.4 or later

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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