FavoriteApplication · Jenkins

CVE-2022-27196

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-15

Fix available

A fix is available. Upgrade to 2.4.1 or later.

See remediation →

58/100

Remediation priority · Elevated

Remotely reachable

Official description

NVD · unedited

Jenkins Favorite Plugin 2.4.0 and earlier does not escape the names of jobs in the favorite column, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure or Item/Create permissions.

Technical summary

dbcve analysis · high confidence

Jenkins Favorite Plugin 2.4.0 and earlier fails to sanitize job names when rendering them in the favorite column, allowing stored XSS. Attackers with Item/Configure or Item/Create permissions can inject malicious JavaScript via job names that executes in the browsers of other users viewing favorites.

MitigationUpdate Jenkins Favorite Plugin to version 2.4.1 or later which properly escapes job names. Restrict Item/Configure and Item/Create permissions to trusted users until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FavoriteApplication

Affected:< 2.4.1

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check if Jenkins Favorite Plugin is installed

Navigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Favorite', or list installed plugins via Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins

Affected if The Favorite plugin appears in the installed plugins list
Determine the installed version of the Favorite Plugin

In the Installed plugins tab, locate the Favorite plugin and read the Version column, or inspect the plugin file at $JENKINS_HOME/plugins/favorite.jpi (or .hpi) and check the manifest

Affected if The displayed version is 2.4.0 or earlier
Verify the vulnerability is exploitable

Review user permissions in Manage Jenkins > Manage Users and under People > check which users have Item/Configure or Item/Create permissions (typically found in configured jobs/folders under Configure > Enable project-based security or in matrix authorization settings)

Affected if Any user with Item/Configure or Item/Create permission is untrusted or the system allows arbitrary job naming by non-administrators
Confirm job names can be viewed in favorites

View the main Jenkins dashboard and check if any jobs display in the Favorite column (starred jobs), or view a user's favorites by clicking the star icon next to jobs

Affected if Favorites are visible and the favorite column renders job names in the UI

The environment is affected if the Jenkins Favorite Plugin version is 2.4.0 or earlier AND users with Item/Configure or Item/Create permissions can create or rename jobs with malicious names that will be rendered in the favorites view.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to 2.4.1 or later

Fixed in 2.4.1

Interim mitigation

Update Jenkins Favorite Plugin to version 2.4.1 or later which properly escapes job names. Restrict Item/Configure and Item/Create permissions to trusted users until patched.

Recommended fix High confidence

Jenkins Favorite Plugin version 2.4.1 or later

Log in to Jenkins as an administrator
Navigate to 'Manage Jenkins' > 'Manage Plugins'
Go to the 'Updates' tab
Locate the 'Favorite' plugin in the list
Select the checkbox next to the Favorite plugin
Click 'Download now and install after restart'
Wait for the plugin to download and install
Restart Jenkins to complete the installation

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

Fix this in Favorite 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-27196 — 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

Primary sources

www.jenkins.ioVendor Advisory
www.openwall.comMailing ListThird Party Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27196 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-27196?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2.4.1 or later

Severity 5.4 Medium

Exploit likelihood EPSS, next 30 days 0.8%

Affects: Favorite

Remediation

Need this fixed?

Fix this in Favorite 5 hrs · Low

Typical engagement from $860

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2022-27196 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References