Lucene SearchApplication · Jenkins
CVE-2022-36922
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 · uneditedJenkins Lucene-Search Plugin 370.v62a5f618cd3a and earlier does not escape the search query parameter displayed on the 'search' result page, resulting in a reflected cross-site scripting (XSS) vulnerability.
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 confidenceJenkins Lucene-Search Plugin versions 370.v62a5f618cd3a and earlier contains a reflected cross-site scripting (XSS) vulnerability where the search query parameter displayed on the search result page is not properly escaped, allowing attackers to inject malicious scripts via the query parameter.
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
Lucene SearchApplication
<= 370.v62a5f618cd3aCVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Lucene-Search plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab and search for 'Lucene Search' in the list of installed pluginsAffected if The Lucene Search plugin appears in the installed plugins list
-
Check installed version of Lucene-Search pluginIn the same Installed Plugins list, locate the 'Lucene Search' plugin and note the Version column valueAffected if The installed version is 370.v62a5f618cd3a or earlier (versions up to and including this version are affected)
-
Determine if search feature is accessibleAttempt to access the Lucene Search functionality in Jenkins - typically found at /search/ or check if the plugin exposes a search endpoint in the Jenkins instanceAffected if The search feature is exposed and accessible to users (unauthenticated or authenticated)
-
Test for reflected XSS in search parameterUse a browser or tool to submit a search query containing a benign test payload (such as <script>alert(1)</script> or a URL-encoded equivalent) to the search endpoint and observe if the payload is rendered unescaped in the responseAffected if The search query parameter value is reflected back in the page HTML without proper encoding/escaping
A user is affected if the Lucene-Search plugin is installed with version 370.v62a5f618cd3a or earlier AND the search feature is accessible, with the injected script executing in the browser when the malicious query is submitted.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Jenkins Lucene-Search Plugin to version 370.v62a5f618cd3a or later which includes proper output encoding for the search query parameter.
Upgrade to Lucene Search plugin version 371.v7b_1d9a_b_04d9 or later (check Jenkins update center for latest available version)
- 1. Navigate to Manage Jenkins > Manage Plugins
- 2. Go to the 'Installed' tab
- 3. Find 'Lucene Search' plugin in the list
- 4. If an update is available, select it and click 'Update'
- 5. Restart Jenkins or wait for the plugin to update
- 6. Alternatively, manually download the fixed plugin from the Jenkins update center or GitHub releases
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Lucene Search
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36922 in production — separate from our analysis above.
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.
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.
- 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